Doramagic Project Pack · Human Manual

strategy-skills

Related topics: Entrypoints and Runtime Surface, Architecture Evidence Map, Operations and Verification Boundaries

Repository Overview

Related topics: Entrypoints and Runtime Surface, Architecture Evidence Map, Operations and Verification Boundaries

Section Related Pages

Continue reading this section for the full explanation and source context.

Section Understand where you are

Continue reading this section for the full explanation and source context.

Section Decide and build

Continue reading this section for the full explanation and source context.

Section One-command install (Claude Code, Cursor, Codex, and 40+ agents)

Continue reading this section for the full explanation and source context.

Related topics: Entrypoints and Runtime Surface, Architecture Evidence Map, Operations and Verification Boundaries

Repository Overview

This page is generated from repository evidence because the Human Wiki provider was unavailable. It intentionally limits itself to README and file-tree facts.

README Evidence

Eterdis Strategy Skills

Open strategy frameworks designed to run as AI-guided conversations. Each skill is a single markdown file that turns any large language model into a strategy thinking partner.

Built on 20 years of consulting practice. Free, open, model-agnostic.

What these are

Strategy skills are structured prompts in SKILL.md format that guide an LLM through a proven strategic framework — asking the right questions, spotting patterns, surfacing contradictions, and producing actionable output. They work with Claude, ChatGPT, Gemini, or any model that reads markdown.

Every skill runs in three modes:

  • Diagnostic — deep first-use session (30-60 minutes)
  • Review — periodic re-assessment (15-20 minutes)
  • Alert Triggers — early-warning tripwires to monitor between sessions

All skills read and update a shared company-context.md file that accumulates strategic intelligence across sessions.

Skills

Understand where you are

SkillWhat it does
strategy-diagnosticEntry point — AI-guided strategic assessment that detects which frameworks to run
strategy-mapMap the causal chain from resources to results, expectations to requirements
vrio-analysisTest whether your competitive advantages are real, rare, and durable
environmental-radarContinuous PESTEL scan for external forces shaping your next move
market-positionCompetitive positioning — where you actually stand, not where the slide deck says
wardley-mapComponent evolution mapping — see where the value chain is heading
culture-assessmentSurface the real culture vs. the stated one

Decide and build

SkillWhat it does
first-principles-strategyFind the theoretical maximum, then work backwards to your first move
playing-to-winLafley/Martin strategy cascade — five choices that define a winning strategy
pre-mortemIdentify how the plan will fail before it does
protoloop-setupDesign a Track Two innovation system for new revenue streams

Quick start

One-command install (Claude Code, Cursor, Codex, and 40+ agents)


[excerpt truncated]

## Selected Source Inventory

- `README.md`
- `mcp-server/README.md`
- `mcp-server/package.json`
- `mcp-server/src/index.ts`
- `CONTRIBUTING.md`
- `SKILL-TEMPLATE.md`
- `culture-assessment/SKILL.md`
- `environmental-radar/SKILL.md`
- `first-principles-strategy/SKILL.md`
- `install/STRATEGY.md`
- `install/company-context.md`
- `market-position/SKILL.md`

| File | Evidence role | Size |
|---|---|---|
| `README.md` | README/product and usage evidence | 4188 bytes |
| `mcp-server/README.md` | documentation evidence | 2042 bytes |
| `mcp-server/package.json` | package/runtime metadata | 1178 bytes |
| `mcp-server/src/index.ts` | implementation surface | 4289 bytes |
| `CONTRIBUTING.md` | documentation evidence | 3204 bytes |
| `SKILL-TEMPLATE.md` | documentation evidence | 2168 bytes |
| `culture-assessment/SKILL.md` | documentation evidence | 18991 bytes |
| `environmental-radar/SKILL.md` | documentation evidence | 12989 bytes |
| `first-principles-strategy/SKILL.md` | documentation evidence | 26409 bytes |
| `install/STRATEGY.md` | documentation evidence | 17420 bytes |
| `install/company-context.md` | documentation evidence | 3499 bytes |
| `market-position/SKILL.md` | documentation evidence | 15655 bytes |

Source: `[README.md:1-120]()`

Source: https://github.com/eterdis/strategy-skills / Human Manual

Entrypoints and Runtime Surface

Related topics: Repository Overview, Architecture Evidence Map, Operations and Verification Boundaries

Section Related Pages

Continue reading this section for the full explanation and source context.

Related topics: Repository Overview, Architecture Evidence Map, Operations and Verification Boundaries

Entrypoints and Runtime Surface

The files below are the highest-signal candidates for how the project is installed, started, configured, or embedded. Treat this as an evidence map, not an inferred API contract.

FileEvidence roleSize
README.mdREADME/product and usage evidence4188 bytes
mcp-server/README.mddocumentation evidence2042 bytes
mcp-server/package.jsonpackage/runtime metadata1178 bytes
mcp-server/src/index.tsimplementation surface4289 bytes
CONTRIBUTING.mddocumentation evidence3204 bytes
SKILL-TEMPLATE.mddocumentation evidence2168 bytes
culture-assessment/SKILL.mddocumentation evidence18991 bytes
environmental-radar/SKILL.mddocumentation evidence12989 bytes
first-principles-strategy/SKILL.mddocumentation evidence26409 bytes
install/STRATEGY.mddocumentation evidence17420 bytes
install/company-context.mddocumentation evidence3499 bytes
market-position/SKILL.mddocumentation evidence15655 bytes

Source: README.md:1-120

Source: https://github.com/eterdis/strategy-skills / Human Manual

Architecture Evidence Map

Related topics: Repository Overview, Entrypoints and Runtime Surface, Operations and Verification Boundaries

Section Related Pages

Continue reading this section for the full explanation and source context.

Related topics: Repository Overview, Entrypoints and Runtime Surface, Operations and Verification Boundaries

Architecture Evidence Map

This section maps source paths into likely architectural areas based on repository layout only. Claims that require execution are intentionally not made here.

Source: mcp-server/README.md:1-120

Source: https://github.com/eterdis/strategy-skills / Human Manual

Operations and Verification Boundaries

Related topics: Repository Overview, Entrypoints and Runtime Surface, Architecture Evidence Map

Section Related Pages

Continue reading this section for the full explanation and source context.

Related topics: Repository Overview, Entrypoints and Runtime Surface, Architecture Evidence Map

Operations and Verification Boundaries

Operational guidance is limited to files that are present in the repository. Before using this project in an agent workflow, verify install, quickstart, and runtime behavior in a sandbox.

Source: mcp-server/package.json:1-120

Source: https://github.com/eterdis/strategy-skills / Human Manual

Doramagic Pitfall Log

Source-linked risks stay visible on the manual page so the preview does not read like a recommendation.

medium Project risk needs validation

The project should not be treated as fully validated until this signal is reviewed.

medium README/documentation is current enough for a first validation pass.

The project should not be treated as fully validated until this signal is reviewed.

medium Maintainer activity is unknown

Users cannot judge support quality until recent activity, releases, and issue response are checked.

medium no_demo

The project may affect permissions, credentials, data exposure, or host boundaries.

Doramagic Pitfall Log

Doramagic extracted 7 source-linked risk signals. Review them before installing or handing real data to the project.

1. Project risk: Project risk needs validation

  • Severity: medium
  • Finding: Project risk is backed by a source signal: Project risk needs validation. Treat it as a review item until the current version is checked.
  • User impact: The project should not be treated as fully validated until this signal is reviewed.
  • Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
  • Evidence: identity.distribution | mcp_registry:io.github.eterdis/strategy-skills:1.0.1 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.eterdis%2Fstrategy-skills/versions/1.0.1 | repo=strategy-skills; install=skills

2. Capability assumption: README/documentation is current enough for a first validation pass.

  • Severity: medium
  • Finding: README/documentation is current enough for a first validation pass.
  • User impact: The project should not be treated as fully validated until this signal is reviewed.
  • Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
  • Evidence: capability.assumptions | mcp_registry:io.github.eterdis/strategy-skills:1.0.1 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.eterdis%2Fstrategy-skills/versions/1.0.1 | README/documentation is current enough for a first validation pass.

3. Maintenance risk: Maintainer activity is unknown

  • Severity: medium
  • Finding: Maintenance risk is backed by a source signal: Maintainer activity is unknown. Treat it as a review item until the current version is checked.
  • User impact: Users cannot judge support quality until recent activity, releases, and issue response are checked.
  • Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
  • Evidence: evidence.maintainer_signals | mcp_registry:io.github.eterdis/strategy-skills:1.0.1 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.eterdis%2Fstrategy-skills/versions/1.0.1 | last_activity_observed missing

4. Security or permission risk: no_demo

  • Severity: medium
  • Finding: no_demo
  • User impact: The project may affect permissions, credentials, data exposure, or host boundaries.
  • Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
  • Evidence: downstream_validation.risk_items | mcp_registry:io.github.eterdis/strategy-skills:1.0.1 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.eterdis%2Fstrategy-skills/versions/1.0.1 | no_demo; severity=medium

5. Security or permission risk: no_demo

  • Severity: medium
  • Finding: no_demo
  • User impact: The project may affect permissions, credentials, data exposure, or host boundaries.
  • Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
  • Evidence: risks.scoring_risks | mcp_registry:io.github.eterdis/strategy-skills:1.0.1 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.eterdis%2Fstrategy-skills/versions/1.0.1 | no_demo; severity=medium

6. Maintenance risk: issue_or_pr_quality=unknown

  • Severity: low
  • Finding: issue_or_pr_quality=unknown。
  • User impact: Users cannot judge support quality until recent activity, releases, and issue response are checked.
  • Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
  • Evidence: evidence.maintainer_signals | mcp_registry:io.github.eterdis/strategy-skills:1.0.1 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.eterdis%2Fstrategy-skills/versions/1.0.1 | issue_or_pr_quality=unknown

7. Maintenance risk: release_recency=unknown

  • Severity: low
  • Finding: release_recency=unknown。
  • User impact: Users cannot judge support quality until recent activity, releases, and issue response are checked.
  • Recommended check: Open the linked source, confirm whether it still applies to the current version, and keep the first run isolated.
  • Evidence: evidence.maintainer_signals | mcp_registry:io.github.eterdis/strategy-skills:1.0.1 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.eterdis%2Fstrategy-skills/versions/1.0.1 | release_recency=unknown

Source: Doramagic discovery, validation, and Project Pack records

Community Discussion Evidence

These external discussion links are review inputs, not standalone proof that the project is production-ready.

Sources 1

Count of project-level external discussion links exposed on this manual page.

Use Review before install

Open the linked issues or discussions before treating the pack as ready for your environment.

Community Discussion Evidence

Doramagic exposes project-level community discussion separately from official documentation. Review these links before using strategy-skills with real data or production workflows.

Source: Project Pack community evidence and pitfall evidence