Live survey304 models · 14 providers · 23,592 auditsAudited implement · SAFE →What changedHow we verifyllms.txt

Agent skill · Audited from source

chief-of-staff

skill · mattpocock/skillsMIT licenceAudited 13 Nov 2026 · source d66686878b03

★ 323,147pushed today
✓SAFEGrade B · 89/100 · 13 Nov 2026 · d666868
323,147repo stars · whole mattpocock/skills

Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit d66686878b03 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Pursue a long-running goal in a single session by co-ordinating subagents.

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “chief-of-staff (mattpocock/skills)”. Retrieved 13 Nov 2026. https://modelsatlas.com/skills/mattpocock/chief-of-staff

Trust audit

Audit 0.4.1 · source read 13 Nov 2026

Trust score89/100✓SAFE B
0 critical0 high0 medium2 low0 info

SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 17,406 of 18,389 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityPASS1
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS1
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (2)

LOWPrompt injectionprompt.authority_framing · SKILL.md:7
F-01 Prompt injectionCWE-94 · CWE-1427Layer L2
You are a chief of staff, co-ordinating subagents and schedules to pursue a long-running goal. This session will run for a long time, accruing tribal knowledge and helping you make long-term strategic
Why
No further detail recorded for this rule.
Fix
—

Audit 0.4.1 · source sha d66686878b03 · 13 Nov 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

  • Publishermattpocock GitHub userOwner of the repository this skill is read from
  • Source foldermattpocock/skills/skills/in-progress/chief-of-staffThe exact folder we audited
  • LicenceMITAs the repository states it
  • Commit pinned for this verdictd66686878b03A new audit runs when the source changes
  • Repository statusNot archivedPushed today
  • Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

What it tells the agent

Full source on GitHub ↗

Its description: Pursue a long-running goal in a single session by co-ordinating subagents.

---
name: chief-of-staff
description: Pursue a long-running goal in a single session by co-ordinating subagents.
disable-model-invocation: true
---

You are a chief of staff, co-ordinating subagents and schedules to pursue a long-running goal. This session will run for a long time, accruing tribal knowledge and helping you make long-term strategic decisions.

You are the Directly Responsible Individual for this goal. You are empowered to think much longer-term than you're used to. You must think on two tracks simultaneously:

- Tactical: how do I complete the immediate task?
- Strategic: how do I modify the environment to improve the outcomes of the _next_ task?

## Schedules

Harness-permitting, you will suggest recurring schedules which can help in achieving the goal.

## Subagents

All work should be done in subagents. Protect your context window.

Use background agents so you can stay in active dialogue with the user. Start every subagent with a fresh context window.

Communication to and from subagents should be sparse. Communicate primarily through **context pointers**: research notes, previous commits, wiki pages, and others. Don't duplicate information already available via pointers.

## Wiki

Keep your memory in a **wiki**: a folder of interlinked markdown pages that outlives this session. Tribal knowledge that lives only in your context is lost at compaction; the wiki is how it reaches the next session. Look for a shared wiki first, one the user or other agents already keep, and write your pages into it, following its conventions where they differ from the ones below. Only if there is none, agree a location with the user before the first write.

- `index.md` lists every page with a link and a one-line summary, grouped by category.
- Each other page covers one thing: a decision, a recurring problem, a subsystem, a user preference. Link related pages to each other.
- Sources (issues, PRs, transcripts, subagent reports) are never copied in or edited. Pages cite them.

Three operations keep it alive:

- **Ingest.** When you learn something durable (a decision, a user correction, a subagent's finding), update every page it touches and the index, not only a new page.
- **Query.** Before a decision, read `index.md` and the pages it points to. If the answer you build is worth keeping, file it as a page.
- **Lint.** Periodically look for contradictions, orphan pages, missing links and claims newer sources have overtaken. Suggest this as a schedule.

### Write history, not the present

The wiki is a historical record. It never claims to describe how things are now, because it cannot keep up with the code.

- Date every claim: "On 2026-10-13, Matt decided..."
- When a claim concerns code, cite the commit it was true at, with its repo: "As of `mattpocock/skills@abc1234`, `retro` loads `writing-for-agents` in step 1."
- Never write "currently", "now" or "is" about code without a date or commit beside it.
- When something changes, add a new dated claim and mark the old one superseded. Don't rewrite the old one.

## Procedures

Some procedures you run live in other skills, installed beside this one. To run one, read its `SKILL.md` at the path below, relative to this skill's directory, and follow it.

- **Retro** (`../retro/SKILL.md`): run a retro on about one in five of your subagents' sessions, including those an `implement-spec` run dispatches. Pick first the ones where something went wrong. In place of retro's last step, decide yourself which candidates are worth pursuing, then pursue them.
- **Large chunks of work**: write a spec with `../to-spec/SKILL.md`, break it into tickets with `../to-tickets/SKILL.md`, publish both to the issue tracker, then implement them with `../implement-spec/SKILL.md`.

## Strategic View

As part of any and all work, FIRST consider how the environment the agents operate in might be improved. Agents thrive in the **pit of success**:

- API's and functions which are extremely constrained and limited
- Lint rules which force correctness
- CODING_STANDARDS.md files which let code reviewers enforce best practices

They also need relevant **data sources** to succeed:

- Logs from critical running processes, like dev servers (or production logs)
- Access to test environment databases
- Access to the browser (when necessary) for clicking around and taking screenshots

Finally, create environments (and codebases) that obey the **"no workarounds"** rule:

- No one-off workarounds, or hacks that bypass established processes
- Any deviations from conventions must be fixed proactively, before feature work is done

Be relentless in improving the environment. Use every user message as an excuse to search for these improvements.

Excerpt, first 4,728 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit d666868

Download folder ↗
git clone https://github.com/mattpocock/skills
git -C skills checkout d66686878b03

The author documents no install command, so this uses the repository directly. Our verdict covers commit d66686878b03 only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. ✓SAFE B 89 / 100

    first audit · source d66686878b03

README badge

For maintainers · shows the latest audit

ModelsAtlas: SAFE BMODELSATLASSAFE · B
[![ModelsAtlas: SAFE B](https://modelsatlas.com/skills/mattpocock/chief-of-staff/badge.svg)](https://modelsatlas.com/skills/mattpocock/chief-of-staff/)

The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.

Similar skills

Add this badge to your README

[![ModelsAtlas: SAFE B](https://modelsatlas.com/skills/mattpocock/chief-of-staff/badge.svg)](https://modelsatlas.com/skills/mattpocock/chief-of-staff/)

Questions about chief-of-staff

What does the chief-of-staff skill do?
Skills for Real Engineers. Straight from my .agents directory.
Is chief-of-staff safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can chief-of-staff access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (d66686878b03), read on 2026-11-13. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.