Knowhere Growth Content Skill

Portable agent skill for researching Semrush keyword opportunities, analyzing competitor content, and producing Knowhere API article briefs, draft packs, QA reports, and publish-ready markdown articles.

This repository is intended to be installed with the open skills CLI into any supported AI IDE or agent workspace:

npx skills add Ontos-AI/knowhere-growth-content-skill --skill seo-content-writer -a <agent>

Repository Layout

skills/
└── seo-content-writer/
    ├── SKILL.md
    ├── package.json
    ├── agents/
    ├── assets/
    ├── references/
    ├── scripts/
    └── templates/

The skill is under skills/ because npx skills add discovers skills in that directory.

Install

Install into the current project for one AI IDE:

npx skills add Ontos-AI/knowhere-growth-content-skill --skill seo-content-writer -a <agent>

Examples:

npx skills add Ontos-AI/knowhere-growth-content-skill --skill seo-content-writer -a cursor
npx skills add Ontos-AI/knowhere-growth-content-skill --skill seo-content-writer -a antigravity

Install globally:

npx skills add Ontos-AI/knowhere-growth-content-skill --skill seo-content-writer -a <agent> -g
npx skills add Ontos-AI/knowhere-growth-content-skill --skill seo-content-writer -a cursor -g

Install from a direct GitHub URL:

npx skills add https://github.com/Ontos-AI/knowhere-growth-content-skill --skill seo-content-writer -a cursor

Install for multiple AI IDEs:

npx skills add Ontos-AI/knowhere-growth-content-skill --skill seo-content-writer -a cursor -a antigravity

If an AI IDE is not supported by the skills CLI, copy skills/seo-content-writer/ into that agent's local skills directory and point the agent to SKILL.md.

Configure Semrush

In the operator workspace root, create .env.local:

SEMRUSH_API_KEY=your_semrush_api_key
SEMRUSH_DATABASE=us

Do not put the Semrush API key inside seo-content-skill.config.json.

This is a public repository. Keep secrets, private product repositories, unpublished internal documents, and generated content out of git.

Configure Workspace Sources

In the operator workspace root, create seo-content-skill.config.json.

Start from the example config in the installed skill.

The installed path depends on the AI IDE. Examples:

cp .agents/skills/seo-content-writer/assets/example-config.json seo-content-skill.config.json
cp ~/.cursor/skills/seo-content-writer/assets/example-config.json seo-content-skill.config.json

Then update:

• sourceRoots
• primarySources
• competitorDomains
• competitorRepos

Install Script Dependencies

This skill includes TypeScript helper scripts. It is Node.js/npm-first because npx skills add already requires Node.js and npm. Bun is not required.

After installation, install dependencies inside the installed skill directory.

Because installation paths differ by AI IDE, first locate the installed seo-content-writer skill directory, then install from there:

Examples:

cd <installed-skill-dir>
npm install

Agents can also run this installation step automatically when they first need the scripts.

Use

In any supported AI IDE or agent workspace, ask naturally. Operators do not need to remember the internal workflow:

Create a publish-ready English markdown article for Knowhere API about RAG document chunking. Use Semrush and workspace context.

If the IDE supports explicit skill mentions:

@seo-content-writer
Create a publish-ready English markdown article for Knowhere API about RAG document chunking. Use Semrush and workspace context.

The agent should orchestrate:

context -> Semrush research -> cluster selection -> brief -> draft pack -> draft -> QA -> final revision -> final check

Generated artifacts are written to:

seo-content-output/

Trigger Conditions

The skill should trigger when the user asks for:

• seo-content-writer, SEO Content Writer, Knowhere SEO skill, Knowhere content writer skill, or Semrush writer skill
• Knowhere API product marketing content
• Semrush keyword research
• long-tail, low-competition, or high-ROI keyword discovery
• competitor traffic or content opportunity analysis
• editorial briefs, draft packs, markdown drafts, QA reports, or final articles
• content around RAG ingestion, document parsing, document chunking, structured parsing, PDF parsing APIs, or retrieval quality

The skill should not be used for unrelated generic writing tasks or site implementation work such as Next.js metadata, sitemap, schema, canonical URLs, or deployment.

Local Smoke Test

From this repository root:

cp skills/seo-content-writer/assets/example.env.local .env.local
# edit .env.local and set SEMRUSH_API_KEY

cp skills/seo-content-writer/assets/example-config.json seo-content-skill.config.json

cd skills/seo-content-writer
npm install
npm run semrush:check -- --workspace ../..
npm run context:inspect -- --workspace ../..

Generated files are written to seo-content-output/ and are ignored by git.

Do Not Commit

Do not commit:

• .env.local
• seo-content-output/
• seo-content-skill.config.json
• node_modules/
• local product source repos used only for development