action-runner
Turn a skill's recommendations into real, executed actions — open the tickets, file the issues, post the updates — safely: dry-run preview, risk-classified, approval-gated, then recorded back to the brain. Use when asked to act on a plan, file tickets from a checklist, create issues from a PRD, execute the recommended next steps, or wire a skill's output into GitHub/Linear/Slack. Produces a dry-run actions plan with per-action risk, executes only after approval via the connected action MCP, and logs what was done. Nothing acts silently.
npx skills add mohitagw15856/pm-claude-skills --skill action-runner --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Action Runner Skill The library is great at *recommending* work. This skill executes it — the action layer of the [Professional Brain](../professional-brain/SKILL.md) (Phase 2). A skill says "open a ticket per checklist item"; this turns that into real GitHub/Linear/Slack actions, **safely**: previewed, risk-rated, approved, then recorded. The cardinal rule: **nothing acts silently.** ## What This Skill Produces 1. A **dry-run actions plan** — every proposed action with its target, operation, and **risk**. 2. After approval, the **executed actions** (via the connected action MCP) — outbound/destructive ones gated individually. 3. A **record back to the brain** of what was actually done, with provenance. ## Required Inputs Ask for (if not already provided): - **The recommendations to act on** (a launch checklist, PRD requirements, postmortem follow-ups…). - **The connected action MCP** and **targets** — which GitHub repo / Linear project / Slack channel. Scope is limited to what the user names; never act outside it. - **Approval posture** — what may run with a single OK vs. what needs per-action confirmation. ## How it works ``` recommend → build an actions plan (JSON) → preview +
- What This Skill Produces
- Required Inputs
- How it works
- Supported action targets
- Safety rules (non-negotiable)
- The contract for other skills
- Output Format
- Quality Checks
- Anti-Patterns
echo '<plan json>' | python3 scripts/action_preview.py - echo '<plan json>' | python3 scripts/action_preview.py - --allow-high python3 ../professional-brain/scripts/brain_write.py ./brain decisions "Filed launch tickets" \
What does the action-runner skill do?
Turn a skill's recommendations into real, executed actions — open the tickets, file the issues, post the updates — safely: dry-run preview, risk-classified, approval-gated, then recorded back to the brain. Use when asked to act on a plan, file tickets from a checklist, create issues from a PRD, execute the recommended next steps, or wire a skill's output into GitHub/Linear/Slack. Produces a dry-run actions plan with per-action risk, executes only after approval via the connected action MCP, and logs what was done. Nothing acts silently.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill action-runner --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.