skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
ariadoss/superskills64 installs

content-writer

Content creation leveraging knowledge bases — blog posts, docs, marketing copy, investor updates.

How do I install this agent skill?

npx skills add https://github.com/ariadoss/superskills --skill content-writer
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill is designed to help write content by researching local knowledge bases. It performs read operations on local files and uses bash for searching. While safe in its core logic, it is susceptible to indirect prompt injection if the source documents contain malicious instructions.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Content Writer

Create content by researching your knowledge bases before writing.

Knowledge Bases

Reads from knowledge bases configured in ~/.superskills/knowledge.conf. Each line: name|path|description.

cat ~/.superskills/knowledge.conf

Content Types

TypeAudienceTone
Blog postDevelopers, usersTechnical but accessible
DocumentationDevelopersPrecise, example-driven
Marketing copyProspectsBenefit-focused, concise
Investor updateInvestors, boardData-driven, strategic
Product announcementUsersExciting but honest
Internal memoTeamDirect, context-rich

Workflow

Phase 1: Research

Search knowledge bases for relevant context:

# Search across all configured knowledge bases
for kb_path in $(awk -F'|' '{print $2}' ~/.superskills/knowledge.conf); do
  kb_path="${kb_path/#\~/$HOME}"
  [ -d "$kb_path" ] && grep -rli "topic" "$kb_path" --include="*.md" --include="*.txt" --include="*.html"
done

Read the top 3-5 most relevant files. Note key quotes, data points, and frameworks.

Phase 2: Outline

Before writing, create a structured outline:

  1. Hook — why should the reader care?
  2. Context — what's the situation?
  3. Core argument — what's the insight?
  4. Evidence — data, examples, quotes from knowledge base
  5. Call to action — what should the reader do next?

Phase 3: Draft

Write the full draft:

  • Match the tone to the content type and audience
  • Cite knowledge base sources where relevant (for internal docs)
  • Include concrete examples from the project's domain
  • Avoid jargon unless writing for a technical audience

Phase 4: Review

Check the draft against:

  • Accuracy: Cross-reference claims with knowledge base docs
  • Consistency: Align with project positioning and strategy docs
  • Completeness: Cover all key points from the outline
  • Voice: Match the target audience and content type

Phase 5: Humanize (auto-run /humanize)

Run /humanize on the final draft before delivering it. Its scan-and-fix pass strips AI tells (stock phrases, em-dash spam, template rhythm) without changing facts, so accuracy, positioning, and knowledge-base citations survive intact. If /humanize is not installed (deselected from the pack), skip this phase and deliver the reviewed draft.

Tips

  • Research before writing — always check the knowledge base first
  • End with actionable takeaways
  • For technical content, include code examples
  • For marketing content, lead with benefits not features

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/ariadoss/superskills/content-writer">View content-writer on skillZs</a>