repo-demo-copywriter

Writes repository-grounded demo site copy for JavaScript and TypeScript packages.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/vmitsaras/Agent-Skills --skill repo-demo-copywriter-vmitsaras
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-demo-copywriter
Source: https://github.com/vmitsaras/Agent-Skills/tree/main/skills/docs-seo/repo-demo-copywriter
Command: npx skills add https://github.com/vmitsaras/Agent-Skills --skill repo-demo-copywriter-vmitsaras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Demo and documentation pages for open-source packages often contain generic marketing language, copied README text, or unsupported claims. This Skill inspects the actual repository—README, package metadata, source exports, examples, and tests—before writing copy, so every statement about the project is technically accurate and grounded in real behavior. ## Core Features & Use Cases - Repository-grounded writing: Builds a fact sheet from package.json, public APIs, types, tests, and demos before drafting any copy, and flags claims that cannot be verified. - Complete page content: Produces hero sections, demo introductions, code example explanations, feature descriptions, accessibility notes, and SEO metadata following a structured visitor journey. - Anti-generic-language pass: Systematically removes inflated marketing words and AI-sounding phrasing, replacing them with concrete behavioral descriptions. - Use Case: A maintainer has a form validation plugin whose demo page only shows controls and code. The Skill reads the source and examples, then writes a hero, demo instructions, an explained minimal code example, addon descriptions, and SEO metadata that accurately reflect the plugin's behavior. ## Quick Start Ask the agent to write or rewrite the demo page copy for your JavaScript or TypeScript package based on the repository contents.

Frequently Asked Questions about repo-demo-copywriter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write better copy for my open-source package demo site?▼

Base the copy on the repository itself: read the README, package exports, examples, and tests, then describe concrete behavior rather than adjectives. This Skill automates that process, producing hero text, demo instructions, code explanations, and SEO metadata grounded in verified facts.

How to write a landing page for a JavaScript plugin without marketing fluff?▼

Lead with what the project does and what problem it solves, explain the demo interaction, and show a minimal real code example. Avoid words like seamless, powerful, or effortless, and describe implementation behavior such as event handling, markup requirements, and cleanup instead.

Does this Skill modify my demo site files automatically?▼

No. By default it returns finished copy as text without editing any files. It only modifies content files when you explicitly request implementation, and it avoids changing functional code or page layout.

Can it write copy when the repository has little documentation?▼

Yes. It inspects source exports, TypeScript types, tests, and examples to confirm behavior, then writes only what can be verified. Unconfirmed facts are listed separately for maintainer review rather than replaced with generic marketing text.

When should I not use this demo copywriting approach?▼

Do not use it for README-only audits, pure visual design work, API reference generation from types, or npm package metadata. It is scoped to demo and documentation page copy for JavaScript and TypeScript packages with accessible repository content.