Agent skill · Design & Presentation

autopilot-charter

Decide which of your recurring rituals to put on autopilot — and which to keep manual. Use when asked what to automate, how to set up recurring AI runs, which reports or briefings could run on a schedule, or to design an automation charter for a team. Produces a ritual inventory with automate/assist/keep-manual calls, guardrails per ritual, and a rollout order.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill autopilot-charter --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/autopilot-charter/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Autopilot Charter Skill Inventory the reports, briefings, and reviews you produce on a rhythm, and decide — deliberately — which ones an AI should run on a schedule, which it should only draft, and which stay human. ## What This Skill Produces - A **ritual inventory**: every recurring artifact, its cadence, audience, and inputs - An **automate / assist / keep-manual** call per ritual, with the reason - **Guardrails** for each automated ritual (review gate, failure behaviour, escalation) - A **rollout order** — which ritual to automate first and why ## Required Inputs Ask for (if not already provided): - **The recurring outputs** the user or team produces (weekly updates, monthly reviews, monitors, digests) - **Who consumes each one** and what they do with it - **Where the inputs live** (git, analytics, CRM, inbox, notes) and whether an agent can reach them - **Tolerance for error** per artifact — what happens if a run is wrong or missing? ## Classification Framework Score each ritual on four questions, then classify: | Question | Points toward automating | |---|---| | **Inputs reachable?** Can an agent read the sources without a human fetching them? | Yes | | **Structure stable?*

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Classification Framework
  4. Guardrails (required for every "Automate")
  5. Output Format
  6. Automation Charter: [Team / Person]
  7. Quality Checks
  8. Anti-Patterns
More from pm-claude-skills
All skills →
About this skill
What does the autopilot-charter skill do?

Decide which of your recurring rituals to put on autopilot — and which to keep manual. Use when asked what to automate, how to set up recurring AI runs, which reports or briefings could run on a schedule, or to design an automation charter for a team. Produces a ritual inventory with automate/assist/keep-manual calls, guardrails per ritual, and a rollout order.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill autopilot-charter --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going