New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Pace Plan

by magnus919 in magnus919/agent-skills

Build, coordinate, operate, troubleshoot, exercise, and improve an authorized Primary, Alternate, Contingency, and Emergency communications plan.

MITAuto-check passed

Install Pace Plan

skills CLI
$ npx skills add magnus919/agent-skills --skill pace-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install magnus919/agent-skills pace-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/pace-plan .claude/skills/pace-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pace-plan
GitHub stars
116
Token cost
~2k tokens
SKILL.md length
873 words
Files
16 (incl. references)
Skills in repo
130
Repo updated
First seen
Licence
MIT

At a glance

Build, coordinate, operate, troubleshoot, exercise, and improve an authorized Primary, Alternate, Contingency, and Emergency communications plan.

  • Works in 6 steps: PLAN: Define the mission or essential… → COORDINATE: Assign owners, participants,… → OPERATE: Define contact, check-in,… → …
  • Resilient emergency-communications paths and their ownership
  • SKILL.md covers Safety And Authority, Core Workflow, Path Quality Gate and Unknowns Contract, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Pace Plan is an agent skill from magnus919/agent-skills. Build, coordinate, operate, troubleshoot, exercise, and improve an authorized Primary, Alternate, Contingency, and Emergency communications plan. Use for resilient emergency-communications paths and their ownership, triggers, check-ins, tests, and corrective actions. Do not use for generic incident status messaging, frequency or channel planning, radio programming, or unauthorized transmission and activation.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 18 other files, including reference files (for example `DELIVERY-SPEC.md`, `EVIDENCE-LEDGER.md` and `README.md`). Compatibility notes: No runtime dependency. Local procedures, authorities, regulations, and communication details must be supplied by the user.

The repository describes itself as: Curated collection of AI agent skills for Hermes and other agent frameworks. The licence is MIT.

When your agent uses it

  • Resilient emergency-communications paths and their ownership
  • Corrective actions
  • Generic incident status messaging
  • Channel planning

Example prompts

  • “/pace-plan”

Requirements

  • Compatibility (from SKILL.md): No runtime dependency. Local procedures, authorities, regulations, and communication details must be supplied by the user.

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. PLAN: Define the mission or essential function and every sender/receiver pair that must communicate. Inventory only authorized and…
  2. COORDINATE: Assign owners, participants, decision authority, activation authority, and handoffs. Validate that both ends can use each path.
  3. OPERATE: Define contact, check-in, escalation, fallback, activation, and abandonment procedures with observable criteria.
  4. TROUBLESHOOT: Check the expected tier, endpoint readiness, dependencies, and evidence before recommending a transition or handoff.
  5. EXERCISE: Design an authorized, bounded test with objectives, safety limits, expected evidence, and a stop condition. Exercise paths only…
  6. IMPROVE: Record findings, corrective actions, owners, due dates, validation actions, plan changes, unresolved gaps, and the next review.

What it can do on your machine

Read from SKILL.md and the folder at commit c545c2b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    No runtime dependency. Local procedures, authorities, regulations, and communication details must be supplied by the user.

    From compatibility in the SKILL.md frontmatter.

Context cost

Pace Plan loads about 2k tokens when it runs, and up to ~6.2k if it reads all its reference files. Until then it costs about 106 tokens; SKILL.md has 873 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~106
When it runs · the whole SKILL.md, loaded when a task matches
~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from magnus919/agent-skills at commit c545c2b, republished under its MIT licence (© magnus919). 873 words, ~1,977 tokens.

Download SKILL.mdSave it as .claude/skills/pace-plan/SKILL.md (or your agent's skills folder). This skill also uses 15 other files; get the full folder from GitHub.
name
pace-plan
description
Build, coordinate, operate, troubleshoot, exercise, and improve an authorized Primary, Alternate, Contingency, and Emergency communications plan. Use for resilient emergency-communications paths and their ownership, triggers, check-ins, tests, and corrective actions. Do not use for generic incident status messaging, frequency or channel planning, radio programming, or unauthorized transmission and activation.
compatibility
No runtime dependency. Local procedures, authorities, regulations, and communication details must be supplied by the user.
license
MIT

PACE Plan

PACE means Primary, Alternate, Contingency, and Emergency. Use this skill to make a group's communications fallbacks operable, testable, and reviewable without inventing local facts or authority.

Safety And Authority

This skill can support live activation, transmission, or tests that change external state. Read-only discovery and document drafting may proceed without confirmation.

Before the first real transmission, activation, live-system test, or other external mutation:

Confirm the target, scope, and rollback path before acting. Read-only discovery may proceed without confirmation.

Also confirm the named activation authority permits the operational action under the applicable procedure. Plan approval by a decision-maker does not by itself authorize activation. Never infer authority from urgency, role labels, access to equipment, or possession of plan details. Destructive actions and irreversible cleanup require an explicit user directive.

Do not invent frequencies, channels, talkgroups, call signs, contacts, infrastructure, regulatory permission, medical or public-safety instructions, or authority to transmit or activate. Defer to authorized operating procedures, applicable regulation, and incident leadership.

Core Workflow

text
PLAN -> COORDINATE -> OPERATE -> TROUBLESHOOT -> EXERCISE -> IMPROVE
  1. PLAN: Define the mission or essential function and every sender/receiver pair that must communicate. Inventory only authorized and available capabilities.
  2. COORDINATE: Assign owners, participants, decision authority, activation authority, and handoffs. Validate that both ends can use each path.
  3. OPERATE: Define contact, check-in, escalation, fallback, activation, and abandonment procedures with observable criteria.
  4. TROUBLESHOOT: Check the expected tier, endpoint readiness, dependencies, and evidence before recommending a transition or handoff.
  5. EXERCISE: Design an authorized, bounded test with objectives, safety limits, expected evidence, and a stop condition. Exercise paths only to the available and authorized extent.
  6. IMPROVE: Record findings, corrective actions, owners, due dates, validation actions, plan changes, unresolved gaps, and the next review.

Path Quality Gate

Evaluate every proposed P/A/C/E path against these CISA-derived questions:

  • Feasible: Are working systems and trained users available at both ends?
  • Acceptable: Can the path be established without interfering with concurrent operations?
  • Suitable: Can it carry the operationally required information?
  • Distinguishable: Does it avoid the failed method and shared dependencies that would fail with it?
  • Complete: Are the method and transition triggers explicit?

Different applications are not demonstrably independent merely because their names differ. When paths share a device, network, power source, provider, site, or other critical dependency, identify whether the anticipated failure would disable both and record the owner's risk decision. Do not declare independence from technology names alone.

If four feasible paths do not exist, preserve missing tiers as explicit gaps. A truthful incomplete plan is safer than invented redundancy.

Unknowns Contract

Never fill a missing plan-local fact with a plausible value. Record:

text
VALUE: UNKNOWN
OWNER: [person or role responsible for resolving it]
VALIDATION ACTION: [observable check that will establish the value]

An unknown authority, trigger, endpoint capability, or required contact blocks approval of the affected path. It does not block documenting the rest of the plan.

Loading Guide

NeedLoadFile
Design a plan or audit path completeness and independencePlan design methodreferences/plan-design.md
Assign authority, align endpoints, or define activation and handoffCoordination and operationreferences/coordination-and-operation.md
Diagnose a failed or degraded pathTroubleshooting methodreferences/troubleshooting.md
Design a drill, after-action review, or improvement cycleExercise and improvementreferences/exercise-and-improvement.md
Audit the domain claims or source limitations behind this skillEvidence basereferences/evidence-base.md
Test description boundaries outside portable output evalsTrigger probesreferences/trigger-probes.md
Show full SKILL.md (346 more words)Show less

Templates

ArtifactUse whenFile
PACE plan worksheetCreating or auditing all four paths for one mission or functiontemplates/pace-plan-worksheet.md
Communications check-in cardGiving participants a concise, approved operating aidtemplates/communications-check-in-card.md
Exercise and after-action reviewPlanning a bounded test and converting observations into corrective actionstemplates/exercise-and-after-action-review.md
Troubleshooting decision logDiagnosing a failure and preserving evidence, decisions, and handoffstemplates/troubleshooting-decision-log.md

Operating Rules

  • Progress through tiers according to the approved plan's triggers, not by improvising a preferred method.
  • Verify sender and receiver readiness; a one-sided path is not feasible.
  • Use the plan-local review and exercise cadence. Do not invent a universal cadence.
  • Keep operational identifiers in the group's protected plan, not in generic examples or public artifacts.
  • When immediate danger exists, route to emergency services and authorized incident procedures rather than improvising operational instructions.
  • If no communication path remains, record the condition and use only preauthorized no-communications procedures.

Completion Gate

The work is complete only when:

  • The named owner and authorized decision-maker approved the plan.
  • Every required communication pair has P/A/C/E entries or explicitly owned gaps.
  • Every path has documented dependencies, triggers, check-ins, abandonment criteria, and recovery or handoff.
  • Sender and receiver capability was validated to the available extent.
  • Intended paths were exercised to the available and authorized extent, with evidence recorded.
  • Findings and corrective actions have owners, validation actions, and review dates.
  • Unresolved gaps remain visible; none were replaced with assumptions.
  • The change record identifies what changed, why, who approved it, and when it will be reviewed.

When Not To Use

  • Use an incident-communications or stakeholder-communications workflow for status updates, audience messaging, and notification copy that do not concern redundant communication paths.
  • Use the group's authorized radio, frequency, channel, spectrum, or deployment procedure for technical programming and allocation details.
  • Use emergency services and incident leadership for immediate life-safety decisions.
  • Do not use this skill as authority to operate equipment, transmit, activate a system, bypass regulation, or override an incident command structure.

Portability

This skill is technology-neutral and host-neutral. It organizes plan-local facts and decisions; it does not replace local procedures, licenses, regulations, equipment manuals, or incident authority.

© magnus919, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 15 other files (references) in pace-plan of magnus919/agent-skills.

  • SKILL.md
  • DELIVERY-SPEC.md
  • EVIDENCE-LEDGER.md
  • README.md
  • VERIFICATION.md
  • evals/evals.json
  • references/coordination-and-operation.md
  • references/evidence-base.md
  • references/exercise-and-improvement.md
  • references/plan-design.md
  • references/trigger-probes.md
  • references/troubleshooting.md
  • templates/communications-check-in-card.md
  • templates/exercise-and-after-action-review.md
  • templates/pace-plan-worksheet.md
  • templates/troubleshooting-decision-log.md

Open the folder on GitHubat commit c545c2b

Compare with similar skills

Pace Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Pace Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pace Plan this skillmagnus919/agent-skills116—~2kAutomated safety check: PassMIT
Executing Nist Rmf Authorization To Operatemukul975/Anthropic-Cybersecurity-Skills34k—~2.2kAutomated safety check: PassApache-2.0
Hermes Agent Skill AuthoringNousResearch/hermes-agent252k—~3.6kAutomated safety check: PassMIT
Configuring Oauth2 Authorization Flowmukul975/Anthropic-Cybersecurity-Skills34k—~1.7kAutomated safety check: PassApache-2.0
Business Operations Skillsalirezarezvani/claude-skills28k—~2.3kAutomated safety check: PassMIT
Authoring Skillsvercel/next.js143k—~1kAutomated safety check: PassMIT

Similar skills

  • Executing Nist Rmf Authorization To Operate

    mukul975/Anthropic-Cybersecurity-Skills

    Drive a federal system through the NIST Risk Management Framework (SP 800-37 Rev 2) to an Authorization to Operate (ATO): Prepare, Categorize (FIPS 199), Select a control baseline (FIPS 200 / SP…

    34k GitHub stars~2.2k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed

  • Hermes Agent Skill Authoring

    NousResearch/hermes-agent

    Author in-repo SKILL.md files: frontmatter and structure. An agent skill from NousResearch/hermes-agent.

    252k GitHub stars~3.6k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Configuring Oauth2 Authorization Flow

    mukul975/Anthropic-Cybersecurity-Skills

    Configures secure OAuth 2.0 authorization flows, including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant, covering flow selection, PKCE implementation, token…

    34k GitHub stars~1.7k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed

  • Business Operations Skills

    alirezarezvani/claude-skills

    A skill your agent uses when running, diagnosing, or designing internal business operations — process documentation, vendor SLAs, capacity planning, internal comms, SOP/runbook authoring…

    28k GitHub stars~2.3k tokensUpdated 1 mo ago
    Business, Finance & HRAuto-check passed

  • Authoring Skills

    vercel/next.js

    Official

    How to create and maintain agent skills in .agents/skills/. An agent skill from vercel/next.js.

    143k GitHub stars~1k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Performing Purple Team Exercise

    mukul975/Anthropic-Cybersecurity-Skills

    Performs purple team exercises by coordinating red team adversary emulation with blue team detection validation using MITRE ATT&CK-mapped attack scenarios, real-time detection testing, and…

    34k GitHub stars~3.3k tokensUpdated 1 mo ago
    SecurityAuto-check passed

More from magnus919/agent-skills

All 130 skills in this repo

  • Artifact Pyramids

    magnus919/agent-skills

    Organize durable agent research outputs as summaries, analysis, and evidence dossiers.

    116 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed

  • Ascii City Engine

    magnus919/agent-skills

    Build portable, first-person colored ASCII city engines and small GIS-derived city packs.

    116 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Color Management

    magnus919/agent-skills

    Manage color workflows with ICC profiles, working spaces, gamut mapping, and color science.

    116 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check: notes

  • Data Scientist

    magnus919/agent-skills

    A skill your agent uses for PhD-level expertise in data science, statistics, and machine learning: rigorous statistical analysis, experimental design, causal inference, advanced modeling, research…

    116 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

  • Docker Compose

    magnus919/agent-skills

    Use Docker Compose to define, run, debug, and harden multi-container applications.

    116 GitHub stars~2k tokensUpdated yesterday
    Auto-check: notes

  • Fpga Development

    magnus919/agent-skills

    Design, review, simulate, and verify FPGA logic using explicit RTL contracts, clock and reset models, CDC analysis, timing constraints, and reproducible implementation evidence.

    116 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed

Questions about Pace Plan

What does Pace Plan do?

Build, coordinate, operate, troubleshoot, exercise, and improve an authorized Primary, Alternate, Contingency, and Emergency communications plan. Pace Plan is an agent skill from magnus919/agent-skills. Build, coordinate, operate, troubleshoot, exercise, and improve an authorized Primary, Alternate, Contingency, and Emergency communications plan.

When should I use Pace Plan?

Pace Plan fits situations like: resilient emergency-communications paths and their ownership; corrective actions; generic incident status messaging; channel planning.

How do I install Pace Plan in Claude Code?

Run `npx skills add magnus919/agent-skills --skill pace-plan -a claude-code`. Or copy the skill folder (pace-plan in magnus919/agent-skills) into .claude/skills/pace-plan in your project. Claude Code loads it when a task matches its description.

How do I install Pace Plan in Codex?

Run `npx skills add magnus919/agent-skills --skill pace-plan -a codex`. Or copy the skill folder (pace-plan in magnus919/agent-skills) into .agents/skills/pace-plan in your project. Codex loads it when a task matches its description.

Can I use Pace Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add magnus919/agent-skills --skill pace-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pace-plan, .gemini/skills/pace-plan, .github/skills/pace-plan and .opencode/skills/pace-plan in your project.

What does Pace Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Pace Plan is instructions for the agent only. Compatibility (from SKILL.md): No runtime dependency. Local procedures, authorities, regulations, and communication details must be supplied by the user..

Does Pace Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Pace Plan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Pace Plan use?

Pace Plan is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Pace Plan use?

About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.2k tokens, read only when the agent opens those files.

What are the alternatives to Pace Plan?

Skills that share tags, products or a category with Pace Plan: Executing Nist Rmf Authorization To Operate (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Hermes Agent Skill Authoring (NousResearch/hermes-agent, 252k stars), Configuring Oauth2 Authorization Flow (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Business Operations Skills (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pace Plan?

magnus919 (a GitHub user) maintains it in magnus919/agent-skills, which has 116 GitHub stars. The repository holds 130 skills in this directory. The repository was last updated on October 8, 2026.

Source: magnus919/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.