← all skills
whose-turn

whose-turn:whose-turn v1.0.4

Answer what is waiting on the user, what changed and what is on their to-do list from the local Whose Turn monitor, and write to-dos, workspace config and monitor bug reports back to it.

🎯trig84/85πŸ›‘scan8/8
install /plugin install whose-turn@bladeforge

see it

fires when

Use when the user asks what is going on with their tasks, what is waiting on them, what changed, or whose turn it is, in any language; asks to add, finish or list a personal to-do or something not to forget; wants to connect a source or set up the monitor, open its window, or file a bug or an idea about the monitor itself. Reads and writes the local Whose Turn monitor instead of querying Jira, GitHub or Linear again.

best for

A machine running the Whose Turn monitor, in any session where the user asks about their tasks across Jira, GitHub or Linear, keeps personal to-dos, pastes a hand-off from the monitor window, or wants to file something about the monitor itself.

measured Β· trigger

best score
84/85
description-triggering
accuracy
99%
vs baseline β€”
runs/query
5
model claude-opus-5-5
measured 2026-11-03

measured Β· quality

Not measured yet. A quality number needs its own eval: 15 or more tasks, each run with the skill and without it.

security scan Β· 8/8

βœ“prompt-injectionSKILL.md and both hooks frame comment, feed and hand-off text from the sources as data, never instructions; hand-off blocks escape a closing tag. The 2026-11-03 rewrite of the description (RMA-247) only drops quoted Russian phrases; it adds no directive and no new behaviour. 2026-11-03 (RMA-213, RMA-214): the body now names the gone row group and tells the agent to answer a pasted hand-off from the hand-off and the monitor rather than the trackers; no directive that widens access.
βœ“data-exfiltrationAll calls go to the monitor on 127.0.0.1. The only off-box send is a bug or idea report the user asks for, which the monitor files into a Linear project it is configured with; disclosed in metadata.yaml.
βœ“secret-detectionNo key or token in the skill, scripts or fixtures; a token the user pastes goes to the local monitor on stdin, never on a command line or into config.
βœ“dangerous-commandsNo destructive shell. The scripts run npm install into the monitor's own data directory, launchctl/systemctl start of the user's own agent, and the package's install.sh/open.sh.
βœ“obfuscationPlain Node and markdown; nothing encoded or eval'd.
βœ“external-fetchesbin/app.mjs installs the published whose-turn npm package from the npm registry with --ignore-scripts and runs it: the first start takes `latest` (WHOSE_TURN_APP_VERSION names another version), and after that the server updates itself from the `latest` dist-tag; the SessionStart hook starts an available update and says so on its line. Unpinned by design and disclosed in README, plugin.json and metadata.yaml; npm checks each tarball's integrity, and releases carry provenance from the package's own GitHub Actions workflow.
βœ“credential-accessNo read of ~/.ssh, ~/.aws, .env, a keychain or a token store.
βœ“privilege-escalationNo sudo or setuid. app.mjs install, run on the user's request, registers a per-user launchd agent or systemd user unit (the monitor's declared start-at-login); the SessionStart hook only repoints an agent the user already registered when its server.mjs is gone or outdated. Disclosed in metadata.yaml.
scanned 2026-11-03 Β· cerberus:security-scan

side effects & deps

networkfilesotherhook
needsnothing

what’s inside

SKILL.md7.7 KB
metadata.yaml1.3 KB
evals/result.json8.6 KB
evals/rubric.json2.7 KB

SKILL.md

Full instructions live in the repo β€” read SKILL.md on GitHub β†— Β· 4 files in the bundle.