tell-proof: Skill for Cursor

.cursor/skills/tell-demo-script/SKILL.md

tell-demo-script is a skill for Cursor from ashishpatill/tell-proof. It costs 54 tokens per session (376 once invoked), scanned A, original, MIT.

A rehearsal guide for presenting Tell, a tool that checks websites for generic visual patterns and suggests design changes. It covers the demo story, timing, rules, and backup plan.

In plain words
What is it for?
Use it to rehearse the Tell demo, write supporting copy, update contribution notes, and prepare fallback materials.
Why use it?
It keeps a short product demonstration focused and helps avoid missing required compliance or attribution details.

Skill for Cursor

Written for Cursor: installed under .cursor/. Also seen: mentions subagents.

This is ashishpatill/tell-proof's own configuration. It tells Cursor how to work on tell-proof itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything tell-proof configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ashishpatill/tell-proof. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ashishpatill/tell-proof/master/.cursor/skills/tell-demo-script/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ashishpatill/tell-proof

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for tell-demo-script

README.md
[![agentmods](https://agentmods.dev/badge/skills/ashishpatill/tell-proof/tell-demo-script/github.svg)](https://agentmods.dev/skills/ashishpatill/tell-proof/tell-demo-script)
Your own site
<a href="https://agentmods.dev/skills/ashishpatill/tell-proof/tell-demo-script"><img src="https://agentmods.dev/badge/skills/ashishpatill/tell-proof/tell-demo-script/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for tell-demo-script

Your own site · 80×15
<a href="https://agentmods.dev/skills/ashishpatill/tell-proof/tell-demo-script"><img src="https://agentmods.dev/badge/skills/ashishpatill/tell-proof/tell-demo-script.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 376 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.00376
Opus 5 $0.00027 $0.00188
Sonnet 5 $0.00011 $0.00075
Haiku 4.5 $0.00005 $0.00038

Measured 6d ago against content hash 7b549ad59a1f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

tell-demo-script scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/skills/tell-demo-script/SKILL.md · 43 lines

What it actually says

Tell demo script

5 beats (~3 minutes)

  1. Setup (20s) — Paste GitHub repo or live URL. "Shipped in a day with AI. Looks familiar."
  2. Capture + diagnose (30s) — Report loads with named tells and score line.
  3. Taste (50s) — Click SystemFontTell; then an intentional brutalist finding.
  4. Before/after (40s) — Drag reveal seam; call out contrast floor.
  5. Voice + reconcile (40s) — "Warmer, more editorial." Draft fix → Apply in Cursor.

Demo-facing success

  • Loop is visual, not architectural
  • Before/after seam is the aha moment
  • Voice changes direction with text preset fallback
  • Dogfood close: zero tells on Tell itself

Compliance

  • Repo public; original work clearly attributed in CONTRIBUTIONS.md
  • Fixture labeled demo input, not team contribution
  • Not a banned project type (no dashboard-as-product, no basic RAG)
  • Demo highlights in-event work only

Backup plan

If live capture or API fails:

  1. Load committed fixtures/reports/tell-report.json
  2. Run seeded fixture on :3001 if needed
  3. Play recorded backup video

Copy authority

  • Persona/journey: USER_STORY.md
  • Critic voice: docs/01_DESIGN_SYSTEM.md §10
  • Delegate string polish to ux-copywriter subagent
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 43 lines · 54 tokens per session scan A 7b549ad59a1f

Subscribe to this mod's changes

tell-demo-script is a skill published in the GitHub repository ashishpatill/tell-proof (1 stars, last pushed 14d ago), licensed MIT. It adds 54 tokens to every session and 376 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

ijfw-ui-spec

Use when the user says: 'ui spec', 'design contract', 'ui audit setup', 'lock the design', 'visual contract', 'ui review setup', or '/ijfw-ui-spec'. Produces UI-SPEC.md as the visual design contract before any frontend or visual-artifact build, and dispatches ijfw-ui-auditor as the final 6-pillar gate.

FerroxLabs/ijfw · 83 tokens

ijfw-design

Use when the user says: 'design', 'redesign', 'UI', 'UX', 'dashboard', 'page', 'component', 'make it look better', 'polish', 'pretty', 'professional', 'user experience', 'layout', 'visual', 'accessibility', 'colors', 'typography', 'brand'.

FerroxLabs/ijfw · 72 tokens

better-design

Build, improve, and review production interfaces with the Better Design MCP. Use for frontend design, UI, UX, interactions, flows, forms, navigation, components, styling, design systems, accessibility, responsive layouts, motion, React Native, Expo, Shopify, Three.js, and product video work, especially when creating…

marvkr/better-design · 77 tokens

Add Claude design-system and accessibility workflows with UX/UI Agent Skills

Use UX/UI Agent Skills when Claude should generate tokens, component specs, accessibility audits, and framework-specific UI code from a repeatable design workflow.

agentskillexchange/skills · 42 tokens

design-maker

name: design-maker description: Used when the Design Brief is complete and the user needs to generate mockups. Reads Product-Spec.md and Design-Brief.md, then generates a complete set of design deliverables through a design tool MCP, including all pages, state variants, component specifications, design tokens…

zxpmail/ReqForge · 0 tokens

design-brief-builder

name: design-brief-builder description: Used when the user wants to define a design style or visual direction, or says something vague like 'I want a premium/sleek/modern look'. Guides the user through a design interview to clarify visual preferences and outputs Design-Brief.md. After Brief is saved, MUST run Next…

zxpmail/ReqForge · 0 tokens