agentleFS
saksham10arora-dotcomsaksham10arora-dotcom/everything-claude-codex/skills/content/SKILL.md

content

Skill74 starsChanged 9 days agoMITView on GitHub

Use when the user mentions "content", "linkedin post", "carousel", "blog", "publish", "queue", "content plan", or "what to post

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use accounts, data and 8 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.
  • MGrinSkill

    accounts

    Read custom Claude and Codex subscription telemetry, switch captured Claude/Codex accounts, or see which accounts mgrin has paused in the accounts plugin.

    Also in 3 projects that use this

  • launch52-aiSkill

    data

    Generate data layer code (Freezed DTOs, repository implementations, data sources) from feature specifications or API references. Creates the bridge between domain entities and external data sources. Use after /domain to implement the data layer.

    Also in 3 projects that use this

  • nilssonrSkill

    seo

    Full SEO workflow for auditing pages and creating SEO-optimized content. Provides checklists with educational explanations aligned with Google Search Central documentation.

    Also in 7 projects that use this

  • insight68Skill

    pricing

    Help figure out pricing for a product or service using minimalist entrepreneur principles. Use when someone is setting prices, considering price changes, or struggling with what to charge.

    Also in 3 projects that use this

  • 0xSeroSkill

    security

    Also in 4 projects that use this

  • eherrerosjSkill

    humanize

    Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive 'Signs of AI writing' guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases. Triggers on: 'humanize', 'make this sound human', 'remove AI writing', 'de-AI', 'sound more natural', 'less robotic', 'too AI-sounding', or when reviewing text that reads like AI output.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read content/queue.md and content/published.md.

    line 8
  2. Distinctive:

    Before drafting, read the 2 to 3 most recent published pieces to match the user's voice.

    line 10
  3. Very specific:

    After publishing, update queue.md and published.md.

    line 14

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

/content: the content machine

Read content/queue.md and content/published.md. Show what's next, what shipped recently, and anything overdue. Ask: "New piece or finishing something in the queue?"

  • Before drafting, read the 2 to 3 most recent published pieces to match the user's voice.
  • Drafts: content/linkedin_posts/, content/blog_posts/, content/twitter_posts/.
  • Draft the whole thing, then ask for feedback. The user edits; it must sound like them.
  • Tie posts to real work and real numbers. End with a link.
  • After publishing, update queue.md and published.md.

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.