agentleFS
noelcetanoelceta/content-engine/.claude/skills/autopilot/SKILL.md

autopilot

Skill9 starsChanged 6 days agoMITView on GitHub

Run brief, write, review and publish for the next N queued keywords. Use when I type /autopilot.

81 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review-bugbot, rename-chat 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.
  • 0mlkrizzz655335vSkill

    review-bugbot

    缺陷导向代码审查。用 Bugbot 子代理找 bug。

    Also in 3 projects that use this

  • 0mlkrizzz655335vSkill

    rename-chat

    重命名当前聊天。按聊天内容改标题。"disable-model-invocation: true

    Also in 3 projects that use this

  • Tsumugii24Skill

    split-to-prs

    Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.

    Also in 4 projects that use this

  • PandelisZSkill

    update-cli-config

    View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.

    Also in 3 projects that use this

  • 32103210Skill

    migrate-to-skills

    Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when you want to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands into the skills directory.

    Also in 3 projects that use this

  • 32103210Skill

    update-cursor-settings

    Modify Cursor/VSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.

    Also in 3 projects that use this

  • +1 more from 32103210
  • +1 more from 0mlkrizzz655335v

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 72 edited versions we read keep these.

  • 2

    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:

    Start a subagent with model: opus to do everything the brief skill does (.claude/skills/brief/SKILL.md) for that keyword.

    line 13
  2. Very specific:

    Run node scripts/publish.mjs drafts/<slug>.md --status draft so it lands in WordPress as a draft.

    line 15
  3. Distinctive:

    Keep each article in its own subagents so one article's research doesn't fill up the context for the next.

    line 18
  4. Distinctive:

    When you're done, give me one line per article: title, word count, markers left, edit link.

    line 19

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

How many articles: $ARGUMENTS (default 1)

For each of the next keywords in data/queue.csv with status=queued, in order:

  1. Start a subagent with model: opus to do everything the brief skill does (.claude/skills/brief/SKILL.md) for that keyword.
  2. Then start a subagent with model: sonnet to do everything the write skill does (.claude/skills/write/SKILL.md), including the editor review (the editor runs on Opus by itself). If notes/<slug>.md has answers, it uses them. If not, it doesn't wait for me: it leaves [ADD: ...] markers where my experience should go.
  3. Run node scripts/publish.mjs drafts/<slug>.md --status draft so it lands in WordPress as a draft.
  4. Set that row's status in data/queue.csv to drafted and put the WordPress edit link in notes.

Keep each article in its own subagents so one article's research doesn't fill up the context for the next. When you're done, give me one line per article: title, word count, markers left, edit link.

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.