agentleFS
opencueopencue/cuecards/.agents/skills/seo-content-writer/SKILL.md

seo-content-writer

Skill8 starsChanged 3 months agoMITView on GitHub

Use when the user asks to "write SEO content"; drafts posts, articles, and landing pages with keywords, headers, snippets, and evidence boundaries. SEO文章写作/内容优化

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use aminer-data-search, auto-target-tracker and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dav-niu474Skill

    aminer-data-search

    使用 AMiner 开放平台 API 进行学术数据查询与分析。当用户需要查询学者信息、论文详情、机构数据、期刊内容或专利信息时使用此 skill。 触发场景:提到 AMiner、学术数据查询、查论文/学者/机构/期刊/专利、学术问答搜索、引用分析、科研机构分析、学者画像、论文引用链、期刊投稿分析等。 支持 6 大组合工作流(学者全景分析、论文深度挖掘、机构研究力分析、期刊论文监控、学术智能问答、专利链分析)以及 28 个独立 API 的直接调用。 即使用户只说"帮我查一下 XXX 学者"或"找找关于 XXX 的论文",也应主动使用此 skill。

    Also in 4 projects that use this

  • dav-niu474Skill

    auto-target-tracker

    自动目标进度追踪器。在对话中检测到目标相关图片(笔记、进度、截图、记录)时,自动调用 VLM 识别关键信息并记录到目标日记。适用于学习管理、健身追踪、工作进度、习惯养成、创作记录等所有目标管理场景。

    Also in 4 projects that use this

  • Liang-MHSkill

    stock_analysis

    获取 A 股、基金和港股的实时行情和技术分析数据

    Also in 4 projects that use this

  • +9 more from dav-niu474

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use ~~SEO tool and ~~search console when connected.

    line 78
  2. Distinctive:

    When a user requests SEO content, run these nine steps:

    line 82

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SEO Content Writer

Creates SEO content that aligns with search intent, integrates keywords naturally, and stays usable for readers.

Quick Start

Write an SEO-optimized article about [topic] targeting the keyword [keyword]
Here's my content brief: [brief]. Write SEO-optimized content following this outline.

Skill Contract

Expected output: a ready-to-use draft plus the standard handoff summary for memory/content/.

  • Reads: the brief, target keywords, entity inputs, quality constraints, and prior decisions from AGENTS.md and the shared State Model when available.
  • Writes: a user-facing content deliverable and reusable summary.
  • Promotes: approved angles, messaging choices, missing evidence, and publish blockers to memory/hot-cache.md and memory/open-loops.md; propose durable decisions as pending-decision items.
  • Primary next skill: content-quality-auditor when the draft is ready for gating.

Handoff Summary

Emit the standard shape from skill-contract.md §Handoff Summary Format.

Data Sources

Use ~~SEO tool and ~~search console when connected; otherwise ask for keywords, intent, and competitors. See CONNECTORS.md.

Instructions

When a user requests SEO content, run these nine steps:

  1. Gather Requirements — confirm primary and secondary keywords, word count, content type, audience, intent, tone, CTA, and competitors.
  2. Load CORE-EEAT Constraints — apply the 16 high-weight items listed in the companion reference.
  3. Research and Plan — analyze the SERP, map keywords, and choose the content angle.
  4. Create Optimized Title — keep it concise, keyword-led, and aligned with intent.
  5. Write Meta Description — include the keyword, value proposition, and CTA.
  6. Structure Content and Write — use a clean H1 > intro > H2/H3 > FAQ > conclusion flow.
  7. Apply On-Page Best Practices — manage keyword placement, readability, snippets, and supporting visuals.
  8. Add Internal / External Links — include relevant internal and authoritative external links.
  9. Run Final SEO + CORE-EEAT Review — score the draft, auto-fix small issues, and surface any decisions that still need the user.

Reference: See references/instructions-detail.md for the compact workflow, pre-write checklist, issue-classification rules, and self-check format.

Example

Sample outcome: a keyword-led H1, optimized meta description, clear H2 structure, FAQ section, and a brief Changes Made block after the self-check. See references/seo-writing-checklist.md for the copy-start checklist and article template.

Content Type Templates

Quick-start patterns for how-to guides, comparisons, listicles, pillar pages, reviews, and FAQ pages live in references/content-structure-templates.md.

Tips for Success

Match intent, front-load value, support claims with evidence, and write for humans before optimizing for the SERP.

Save Results

On user confirmation, save memory/content/YYYY-MM-DD-<topic>.md and promote key conclusions to memory/hot-cache.md.

Reference Materials

Next Best Skill

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.