demo-quality
Guidelines and quality assurance for technical documentation and demo presentation materials.
Install
mkdir -p .claude/skills/demo-quality && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12096" && unzip -o skill.zip -d .claude/skills/demo-quality && rm skill.zipInstalls to .claude/skills/demo-quality
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when writing README, documentation, CLI output, error messages, or preparing demo artifactsKey capabilities
- →Write README documentation
- →Prepare CLI output
- →Draft error messages
- →Prepare demo artifacts
- →Structure problem statements
- →Create quickstart guides
How it works
The skill provides criteria and rules for creating user-facing documentation and demo artifacts, including README structure, CLI output formatting, and error message content.
Inputs & outputs
When to use demo-quality
- →Draft project README
- →Format CLI error messages
- →Prepare demo video walkthough
About this skill
demo-quality
When to use
Writing README, documentation, CLI output, error messages, or preparing demo artifacts.
Judging criteria (equal weight)
Technological Implementation, Design, Potential Impact, Quality of Idea.
Rules
- Treat every user-facing string as demo copy. Judges read the repo, watch the video, run the hosted project.
- README structure: problem statement (2 sentences), Mermaid architecture diagram, quickstart (5 commands or fewer), demo walkthrough, partner integration details.
- CLI output: structured, parseable, color-coded by stage. Show pipeline stage, correlation token, elapsed time on each line.
- Error messages: state what failed, what was expected, what to do next. No apologies.
- Place an open-source license file (MIT or Apache-2.0) at repo root. GitHub About section must detect it.
- Demo video target: 3 minutes. Show the agent detecting a real schema drift, diagnosing it, proposing a patch, passing the Arize gate, applying via GitLab, and writing the audit entry. End-to-end autonomous loop.
When not to use it
- →When not writing user-facing strings
- →When not preparing demo artifacts
- →When not structuring documentation
Limitations
- →Every user-facing string is treated as demo copy
- →README structure must include problem statement, architecture diagram, quickstart, demo walkthrough, and partner integration details
- →Demo video target is 3 minutes
How it compares
This skill offers specific guidelines for structuring documentation and output for demo quality, unlike a generic approach that might lack consistency or clarity for external audiences.
Compared to similar skills
demo-quality side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| demo-quality (this skill) | 0 | 2mo | No flags | Beginner |
| docs-write | 22 | 6mo | No flags | Beginner |
| content-research-writer | 15 | 10mo | No flags | Beginner |
| doc-coauthoring | 16 | 8mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
docs-write
metabase
Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).
content-research-writer
ComposioHQ
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
doc-coauthoring
anthropics
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
research-grants
davila7
Write competitive research proposals for NSF, NIH, DOE, and DARPA. Agency-specific formatting, review criteria, budget preparation, broader impacts, significance statements, innovation narratives, and compliance with submission requirements.
teams-channel-post-writer
daymade
Creates educational Teams channel posts for internal knowledge sharing about Claude Code features, tools, and best practices. Applies when writing posts, announcements, or documentation to teach colleagues effective Claude Code usage, announce new features, share productivity tips, or document lessons learned. Provides templates, writing guidelines, and structured approaches emphasizing concrete examples, underlying principles, and connections to best practices like context engineering. Activates for content involving Teams posts, channel announcements, feature documentation, or tip sharing.
write-docs
tldraw
Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.