Strategy frameworks
Curated collection of AI agent skills for Hermes and other agent frameworks
npx -y skills add magnus919/agent-skills --skill strategy-frameworksAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 25 days oldThe repository was created 25 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 21 stars21 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Structure organizational strategy work: strategic direction, competitive and industry analysis, growth options, capital allocation, acquisitions, and portfolio choices. Use when framing consequential choices about where to compete, how to pursue an opportunity, or how to compare strategic options.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.1 KB, as published. Nobody here has run it
Strategy Frameworks
Use a framework to make assumptions, alternatives, evidence, and trade-offs visible. Select a reference for the decision at hand rather than applying every framework.
| Need | Load |
|---|---|
| Direction, OKRs, values, or a narrative | references/strategic-planning.md |
| Industry structure, positioning, or potential advantages | references/competitive-analysis.md |
| Growth options, maturity states, or market entry | references/growth-strategy.md |
| Capital choices, acquisitions, or a business portfolio | references/resource-allocation.md |
| Provenance and catalog boundaries | references/source-index.md |
Working Method
- State the decision, decision owner, constraints, and evidence available.
- Use the relevant framework to generate questions and options, not a verdict.
- Record assumptions, uncertainties, trade-offs, and conditions that would change the recommendation.
- Pair strategic logic with appropriate financial, customer, technical, legal, or operational analysis.
When Not to Use
- For stakeholder interviews and raw requirement discovery, use
product-discovery. - For feature prioritization, specifications, and product communications, use
product-methodology. - For quantitative scenarios, valuation, unit economics, or capital-model calculations, use
financial-modeling. - For technology adoption posture and architecture governance, use
technology-radar.
Completion
Stop when the artifact names the decision, alternatives, evidence, key assumptions, trade-offs, and next validation or decision step. It should not present a framework classification as a prediction or decision by itself.