plugin/skills/content-tools/SKILL.md
Use this skill when researching a content topic, gathering supporting facts/data, auditing existing content, building a blog content brief, or generating headlines/value-props/feature-to-benefit/FAQ/social-proof copy for a blog post, landing page, or email — the reusable knowledge layer behind /content-creation and /marketing email + social-post operations, providing content research workflows (topic research, data/fact gathering, existing-content audit, blog content brief template) and AI text-generation prompt templates for headline generation, value propositions, feature-to-benefit translation, FAQ generation, and social proof.
npx skillsauth add avav25/ai-assets content-toolsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Reusable knowledge skill for content workflows. Topic research methodology, fact-gathering procedures, content brief template, and AI text-generation prompt templates. Used by /content-creation and /marketing operations that produce blog posts, page content, landing pages, or email copy.
Image-generation workflows live in the companion file image-and-integration-workflows.md in the legacy /content-creation/ directory; load that file when generating visuals.
Systematic research phase before content creation. Applies to blog posts, articles, landing pages, and other public-facing content.
Goal: Understand the topic landscape before writing.
Steps:
Goal: Collect citable data points to strengthen the content.
Steps:
Goal: Identify cross-linking opportunities within the project's blog.
Steps:
Use this brief specifically for blog posts (the general Content Brief Template applies to landing pages — see page-content-patterns.md in /content-creation):
# Blog Content Brief: [Working Title]
## Research Summary
- **Top competing articles**: [3-5 URLs with one-line summaries]
- **Content gap identified**: [what competitors miss]
- **Unique angle**: [what makes this post different]
## Audience
- **Who**: [target reader persona]
- **Knowledge level**: [beginner / intermediate / expert]
- **Search intent**: [informational / commercial / transactional]
## Keywords
- **Primary**: [keyword] — [monthly search volume if known]
- **Secondary**: [keyword 2], [keyword 3]
- **Long-tail**: [question-based keyword for FAQ]
## Outline
1. [H2 section] — [what this covers, estimated word count]
2. [H2 section] — [what this covers, estimated word count]
3. [H2 section] — [what this covers, estimated word count]
...
## Data Points
- [Stat 1] — [source, year, URL]
- [Stat 2] — [source, year, URL]
## Cross-Links
- **Outbound to existing posts**: [post 1], [post 2], [post 3]
- **Inbound from existing posts**: [post A → update to link here]
## Visual Needs
- **Cover image**: [description, style, mood]
- **Inline visuals**: [diagrams, screenshots, illustrations]
## Target
- **Word count**: [range]
- **Reading time**: [X min]
Goal: Generate multiple headline variants for A/B testing.
Prompt template:
You are a conversion copywriter. Write 10 headline variants for [page type].
Product: [product name and one-sentence description]
Target audience: [who they are, what they care about]
Primary benefit: [the #1 outcome for the user]
Tone: [professional/friendly/bold/playful]
Constraints: Max 10 words. No jargon. Specific > clever.
Format: Number each variant. After all 10, mark top 3 with rationale.
Quality filter: Discard headlines that are vague, use clichés ("revolutionize", "game-changer"), or don't communicate a specific benefit.
Prompt template:
Write a value proposition for [product] following this structure:
1. Headline: What is the end benefit? (max 10 words)
2. Sub-headline: Who is it for and what does it do? (1-2 sentences)
3. Bullet points: 3 key benefits (outcome-focused, not feature-focused)
4. CTA: Action-oriented button text (3-5 words)
Context:
- Product: [description]
- Target user: [ICP description]
- Key differentiator: [what makes this unique]
- Competitor alternatives: [what users do today without this product]
Tone: [brand voice description]
Prompt template:
Convert these product features into user benefits.
For each feature:
1. State the benefit (what the user gets)
2. Add emotional hook (why they should care)
3. Write a one-liner combining both
Features:
- [Feature 1]
- [Feature 2]
- [Feature 3]
Audience: [who they are]
Format: Table with columns: Feature | Benefit | Emotional Hook | One-liner
Prompt template:
Generate FAQ entries for [product/feature page].
Context:
- Product: [description]
- Page purpose: [what the page covers]
- Target audience: [who visits this page]
- Common objections: [list known objections]
For each FAQ:
- Question: Written from the user's perspective (natural language)
- Answer: 2-3 sentences. Direct answer first, then context. No marketing fluff
- Generate 8-10 questions covering: pricing, features, security, onboarding, support, comparison, limitations
Format as structured FAQ suitable for JSON-LD schema markup.
Prompt template:
Write social proof copy based on these customer results:
Customer: [name, title, company]
Results: [specific metrics or outcomes]
Quote context: [what problem they had, what they tried before]
Generate:
1. Short testimonial quote (2-3 sentences, first person)
2. Case study headline
3. Metric callout (e.g., "80% faster deployments")
4. Social proof one-liner for near-CTA placement
Tone: Authentic, specific, not salesy. Include real numbers where available.
| Pattern | Used by |
|---|---|
| Topic Research | /content-creation Step 2 (Research and Brief), /marketing trend-research |
| Data and Fact Gathering | /content-creation Step 2, /marketing trend-research |
| Existing Content Audit | /content-creation Step 2 (cross-link planning) |
| Blog Content Brief Template | /content-creation blog-post Step 2 deliverable |
| Headline Generation | /content-creation Step 3 (drafts), /marketing social-post |
| Value Proposition Writing | /content-creation page + landing, /marketing-init Step 3 (messaging) |
| Feature-to-Benefit Translation | /content-creation page, /marketing-init Step 3 |
| FAQ Generation | /content-creation Step 4 (GEO/AEO), /marketing content pages |
| Social Proof Copy | /content-creation page + landing |
/content-creation (blog + page workflows), /marketing (email, social-post, content-repurpose operations)@geo-writer (structure pass after drafting), @humanizer (voice cleanup pass)plugin/skills/content-creation/image-and-integration-workflows.md (image-generation tools and external service integration live alongside /content-creation; not in this knowledge skill)development
Use this skill when running the recurring (daily) knowledge-base rescan for a repo that already has knowledge/.knowledge-sync.yml — the main-thread dispatcher that reads the config, computes the git delta since last_scanned_sha, maps changed paths to affected doc areas, early-exits cheaply when nothing changed, then fans out one Agent(content-writer) per affected area, applies the propose/direct update policy, advances the baseline only on success, and writes an L4 run log — all with the G1 untrusted-content choke-point, secret-scan, deny-list, and budget controls woven in. For first-time setup use /knowledge-sync-init.
development
Use this skill when bootstrapping scheduled knowledge-base sync for a repo that has no knowledge/.knowledge-sync.yml yet — to run one-time setup that detects the knowledge_root from CLAUDE.md/AGENTS.md, maps doc areas to source globs, records opt-in external sources (Linear/Notion/WebFetch, all disabled by default), captures a baseline last_scanned_sha, sets the per-area update policy, generates or seeds knowledge/CONVENTIONS.md, provisions the L4 memory dir, and offers to register the daily routine. Routes ongoing recurring sync operations to /knowledge-sync.
tools
Use this skill when bootstrapping a target repository to be ai-skills-aware — on the first run of any ai-skills workflow in a fresh repo, when adopting the ai-skills plugin in an existing repo, or after upgrading to a plugin version that adds new memory paths or templates, including when the user does not say "init" but asks to "set up" or "onboard" the repo — to detect codebase type, create CLAUDE.md + AGENTS.md scaffolding, initialize the .ai-skills-memory/ directory tree from L1 templates, and configure .gitignore. Idempotent — safe to re-run. Accepts `--codebase-type <type>` and `--overwrite`. Not for re-initializing only memory — use `/memory-init` instead.
tools
Use this skill when extending, repairing, or improving plugin assets, when ingesting a `/feedback` report as a fix-cycle backlog, or when you do not remember which lower-level command is right for the job — the umbrella workflow for ai-skills plugin-asset authoring and maintenance: creating, auditing, fixing, improving, refactoring, and migrating skills, agents, rules, hooks, prompts, schemas, and rubrics inside the plugin. Auto-classifies the request, loads the right knowledge skills (`@prompt-engineering`, `@context-engineering`, `@team-protocols`), and spawns the right subagents (`prompt-engineer`, `system-architect`, `python-engineer`, `software-engineer`, `qa-engineer`, `eval-judge`) via the `Agent` tool.