smithery/aiskillstore

prescriptive-actions

Use when the user asks for recommendations, next steps, best approaches, or “what should I do” guidance to achieve a goal or fix a problem.

Installation

$ npx skills add smithery/aiskillstore --skill prescriptive-actions

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/aiskillstore · top by installs.

npx skills add smithery/aiskillstore

Browse all from smithery/aiskillstore

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,546 B
  • docs SUMMARY.md 171 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Prescriptive Actions Skill

Purpose

Provide actionable guidance: recommended approaches, prioritized steps, options, and tradeoffs.

When to use

Use this skill when the user request is primarily:

  • Recommend / advise / propose
  • “What should I do?”
  • Suggest next steps or an approach
  • Diagnose + prescribe direction (but not a full plan)

Do NOT use if the user explicitly asks for:

  • a roadmap or timeline (use planning-action)
  • a runbook or checklist (use procedural-action)
  • success criteria or tests (use validation-action)

Operating rules

  1. Restate the goal in one line.
  2. Recommend a primary approach.
  3. Provide alternatives when meaningful (A/B).
  4. Make tradeoffs explicit (cost, time, risk, complexity).
  5. Keep steps high-level and directional, not exhaustive.
  6. List assumptions clearly.
  7. Follow safety and legality constraints.

Outputs

Use this structure unless the user specifies otherwise:

Goal

  • One sentence.

Recommended approach

  • 3–6 high-level steps or principles (directional, not detailed).

Alternatives

  • Option A: when to use it
  • Option B: when to use it

Tradeoffs

  • Cost / speed / risk / complexity notes

Key risks

  • Major risks to watch (no mitigation plans unless asked)

Immediate next actions

  • 2–5 concrete starting actions (not a full checklist)