Arnie016 Content Pack
Use this skill when the user has built something and now needs the words to explain, launch, or promote it cleanly.
Quick Start
- Read the project, audience, and main benefit before drafting copy.
- Start from one source truth and derive the rest of the launch copy from it.
- Keep outputs short, reusable, and easy to paste into GitHub, product pages, or social posts.
- Generate only the formats the user will actually use.
Workflow
Core Messaging
- Identify the one-sentence value proposition first.
- Keep tone aligned with the product: practical, playful, premium, or technical.
- Favor concrete product language over empty launch hype.
- If the product is technical, explain the user win before the implementation detail.
Content Outputs
- Produce only the formats the user needs: tagline, README intro, changelog, tweet thread, release post, or listing text.
- Reuse the same core message across formats so the launch feels coherent.
- If the project is highly technical, explain the benefit before the implementation details.
Required Deliverables
- A core message sentence.
- A short tagline or hook.
- A README-ready intro paragraph when the project is code-based.
- At least one distribution format such as tweet copy, changelog summary, or listing text.
Output Rules
- Keep each asset skimmable and paste-ready.
- Avoid repeating the exact same sentence structure across every format.
- Do not overpromise features or results the project does not actually provide.
Editing Guidance
- Optimize for clarity and reuse.
- Keep promotional copy believable and product-grounded.
- Default to short-form assets unless the user asks for a long write-up.
- If the repo already has a strong tone, mirror it instead of resetting the voice.
Resources
agents/openai.yaml: UI metadata and default invocation prompt.assets/: branded icons for repo listings and skill chips.references/content-formats.md: practical format recipes for README intros, launch blurbs, threads, and release notes.