agentleFS
t0ddharrist0ddharris/compound-marketing/.claude/skills/blog/SKILL.md

blog

Skill1 starsChanged 40 days agoNo licenceView on GitHub

Write a blog post from start to finish. Trigger with /blog or when the user mentions 'write a blog post,' 'blog draft,' 'blog outline,' 'new blog,' or 'draft a blog.' Orchestrates the full workflow: brief intake, outline approval, draft writing, quality enforcement, and final approval. For topic planning, see content-strategy. For editing existing drafts, see copy-editing.

  • Reads credentials
  • Installs packages
  • Commits and pushes

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use blog-brand, blog-cannibalization 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.
  • gaznilmuzammil12-progSkill

    blog-brand

    Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, all blog sub-skills auto-load these files before writing or reviewing. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog".

    Also in 4 projects that use this

  • gaznilmuzammil12-progSkill

    blog-cannibalization

    Detect keyword cannibalization across blog posts by extracting primary keywords from titles and headings, clustering semantically similar targets, and flagging posts competing for the same search intent. Supports local-only mode (grep-based) and DataForSEO API mode (Page Intersection endpoint at ~$0.01/call). Outputs severity-scored report with merge or differentiate recommendations. Use when user says "cannibalization", "keyword overlap", "competing pages", "duplicate keywords", "cannibalize".

    Also in 4 projects that use this

  • mkreindelSkill

    serp-features

    Detect SERP features (featured snippet, PAA, image pack, video, knowledge panel, AIO, local pack, sitelinks) that competitors capture for the site's tracked keywords but the site doesn't, and generate per-gap content-restructuring recommendations. Runs as a monthly cron (10th of month) via `scripts/serp-feature-tracker.mjs`, or interactively via `/serp-features {site}`. Output: `_inbox/serp-feature-gaps-{site}-{date}.md` with gaps grouped by recommended action (most map to `/refresh` with feature-specific flags). Use when the user types `/serp-features` or when the monthly cron fires.

    Also in 3 projects that use this

  • timruebenachSkill

    seo-maps

    Maps intelligence for local SEO — geo-grid rank tracking, GBP profile auditing via API, review intelligence across Google/Tripadvisor/Trustpilot, cross-platform NAP verification (Google/Bing/Apple/OSM), competitor radius mapping, and LocalBusiness schema generation from API data. Three-tier capability: free (Overpass + Geoapify), DataForSEO (full intelligence), DataForSEO + Google (maximum coverage). Use when user says "maps", "geo-grid", "rank tracking", "GBP audit", "review velocity", "competitor radius", "maps analysis", "local rank tracking", "Share of Local Voice", or "SoLV".

    Also in 3 projects that use this

  • +8 more from gaznilmuzammil12-prog

The file

Show its rules and text

We split this skill into the rules it gives an agent

39 rules. 0 are common, 29 are distinctive, and 10 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 29

    Distinctive

    This author's own choices. Worth a look.

  • 10

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 16 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.

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.