How do I install the AI Prose skill?

Run npx skillmds@latest add arcasilesgroup/ai-prose in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is AI Prose safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with AI Prose?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is AI Prose free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published AI Prose?

arcasilesgroup (@arcasilesgroup) published this skill. Their other Agent Skills are listed on their SkillMD profile.

AI Prose by arcasilesgroup — Agent Skill

Name: AI Prose
Author: arcasilesgroup

AI Prose

Writes content (blog posts, pitch decks, sprint review summaries, architecture board reports, solution intent documents) with automatic audience targeting (developer/manager/executive). Trigger for 'write a blog post', 'pitch this', 'sprint review summary', 'architecture board doc', 'solution intent for'. Not for documentation artifacts like CHANGELOG or README; use /ai-docs instead. Not for marketing/social content; use /ai-marketing instead. Not for code-level explanations; use /ai-explain instead.

arcasilesgroup 5dce50b 2 files · 6.9 KB Updated Sep 17, 2026

File contents

Prose

Content writing (blog, pitch, sprint-review, architecture-board, solution-intent) with automatic audience targeting. Edit, don't generate — start from what exists (notes, transcripts, data, real output); template language is a failure mode.

Workflow

Applies §10.7 Clean Code (every sentence earns its place; cut filler) and §10.4 DRY (one source of truth — reuse real output, don't regenerate).

Detect content type: blog / pitch / sprint-review / architecture-board / solution-intent / presentation.
Gather source material — notes, transcripts, data, real output.
Pick audience (developer / manager / executive; default developer); apply the tone + jargon table.
Edit, don't generate — every sentence earns its place.
Apply shared rules (active voice, present tense, no filler).

Routing: single sub-command content (default) → handlers/content.md, which dispatches to sub-types internally by the content type in the prompt.

Audience Targeting

Audience	Tone	Detail Level	Jargon
`developer`	Technical, precise	Implementation details	Full technical vocabulary
`manager`	Results-oriented	Impact and timeline	Minimal, explained when used
`executive`	Strategic	Business value and risk	None

Commands

/ai-prose content blog                      # blog post
/ai-prose content pitch                     # elevator pitch
/ai-prose content sprint-review             # sprint review summary
/ai-prose content presentation             # presentation outline
/ai-prose content architecture-board       # architecture decision for review
/ai-prose content solution-intent          # solution intent document
/ai-prose content blog --audience manager  # manager-targeted variant

Shared Rules

Write what users can DO, not what you BUILT.
Active voice. Present tense.
No "basically", "simply", "just".
Every section earns its place — cut anything that doesn't serve the reader.
Audience determines vocabulary, not quality.

Integration

Called by: user directly. Dispatches to: handlers/content.md. See also: /ai-docs (CHANGELOG/README), /ai-marketing (social/outreach), /ai-explain (code-level), /ai-slides (deck rendering).

Examples

User: "write the sprint review summary for this week"

/ai-prose content sprint-review --audience manager

Reads recent commits + closed issues, produces a results-oriented summary with impact + timeline framing, omits implementation jargon.

$ARGUMENTS

---name: ai-prosedescription: Writes content (blog posts, pitch decks, sprint review summaries, architecture board reports, solution intent documents) with automatic audience targeting (developer/manager/executive). Trigger for 'write a blog post', 'pitch this', 'sprint review summary', 'architecture board doc', 'solution intent for'. Not for documentation artifacts like CHANGELOG or README; use /ai-docs instead. Not for marketing/social content; use /ai-marketing instead. Not for code-level explanations; use /ai-explain instead.---# ProseContent writing (blog, pitch, sprint-review, architecture-board, solution-intent) with automatic audience targeting. Edit, don't generate — start from what exists (notes, transcripts, data, real output); template language is a failure mode.## WorkflowApplies §10.7 Clean Code (every sentence earns its place; cut filler) and §10.4 DRY (one source of truth — reuse real output, don't regenerate).1. Detect content type: blog / pitch / sprint-review / architecture-board / solution-intent / presentation.2. Gather source material — notes, transcripts, data, real output.3. Pick audience (developer / manager / executive; default developer); apply the tone + jargon table.4. Edit, don't generate — every sentence earns its place.5. Apply shared rules (active voice, present tense, no filler).Routing: single sub-command `content` (default) → `handlers/content.md`, which dispatches to sub-types internally by the content type in the prompt.## Audience Targeting| Audience | Tone | Detail Level | Jargon ||----------|------|-------------|--------|| `developer` | Technical, precise | Implementation details | Full technical vocabulary || `manager` | Results-oriented | Impact and timeline | Minimal, explained when used || `executive` | Strategic | Business value and risk | None |## Commands```/ai-prose content blog # blog post/ai-prose content pitch # elevator pitch/ai-prose content sprint-review # sprint review summary/ai-prose content presentation # presentation outline/ai-prose content architecture-board # architecture decision for review/ai-prose content solution-intent # solution intent document/ai-prose content blog --audience manager # manager-targeted variant```## Shared Rules- Write what users can DO, not what you BUILT.- Active voice. Present tense.- No "basically", "simply", "just".- Every section earns its place — cut anything that doesn't serve the reader.- Audience determines vocabulary, not quality.## IntegrationCalled by: user directly. Dispatches to: `handlers/content.md`. See also: `/ai-docs` (CHANGELOG/README), `/ai-marketing` (social/outreach), `/ai-explain` (code-level), `/ai-slides` (deck rendering).## ExamplesUser: "write the sprint review summary for this week"```/ai-prose content sprint-review --audience manager```Reads recent commits + closed issues, produces a results-oriented summary with impact + timeline framing, omits implementation jargon.$ARGUMENTS

Frequently asked questions