action-runner

Featured

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.

AI & Automation 1,228 stars 220 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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 + risk-gate → approve → execute → record ``` 1. **Build the plan** — express each action as JSON: `{"target","op","args","why","risk?"}`. 2. **Preview + gate** — run the helper; it prints a dry-run, classifies risk (🟢 low / 🟡 medium / 🔴 high), and **refuses to proceed while any 🔴 ou...

Details

Author
mohitagw15856
Repository
mohitagw15856/pm-claude-skills
Created
5 months ago
Last Updated
today
Language
HTML
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

skill-advisor

Pre-execution assistant that builds a full execution plan with installed skills (✅) AND uninstalled gaps (❌) the task needs, then offers to install missing skills one by one. Use BEFORE starting any multi-step task. Triggers: 'recommend skills', 'what skill should I use', 'advise', 'suggest', 'help me with', or any work instruction involving code, design, planning, debugging, docs, testing, commits, PRs, strategy.

2 Updated 1 weeks ago
j4rk0r
AI & Automation Listed

action-permissions

Use when you need to look up, grant, or revoke permissions for a specific action (git push, git pull, Slack send, rm -rf, etc.) across skills, cron jobs, scheduled routines, and settings.json. Also use when user asks "is X allowed", "what can my cron do", "add permission for Y", or "remove permission for Z".

0 Updated today
bb25see-hash
AI & Automation Solid

suede-recommend-next-action

Next-action selector for this pack: reads current repo, terminal, plan, or handoff state, scores 2-4 candidate moves against goal alignment, unblocking, evidence, urgency, and leverage, and returns one recommended action plus a short, self-contained copy/paste prompt — expanding into a full operator prompt or granular steps only on request. Use when the user asks 'what's next', 'what should I do next', 'recommend the next move', 'give me the prompt', 'expand prompt', or 'make it granular', especially after a review, audit, plan, or stalled task. NOT FOR: executing the recommended action without the user's separate authorization, or coordinating a multi-lane build across specialists (use suede-agent-teams).

165 Updated today
JasonColapietro