systems-analysis
Skill3 starsChanged 24 days agoApache-2.0View on GitHub
Map system dependencies, feedback or throughput constraints using Cognition OS systems models.
In this repository11 other files it gives its agents.
- adversarial-reviewSkill
- artifact-qualitySkill
- case-intelligenceSkill
- cognition-orchestratorSkill
- cognitive-masterySkill
- executive-synthesisSkill
- framework-composerSkill
- quantitative-decisionSkill
- root-cause-analysisSkill
- setupSkill
- strategic-decisionSkill
The file
Files
Systems Analysis
Required: system boundary and available process or relationship evidence. Optional: capacities, demand, initial stocks, flow units, actors, delays and horizon. Choose FW-17..FW-23 and FW-25 as appropriate. Complete TOC's identify, exploit, subordinate, elevate and repeat loop. For causal loops label polarity, mechanism and delay; distinguish hypothesized relationships from observations. For Wardley map dependencies and evolution independently of visibility. Compute stock/flow or CPM with explicit units if needed. Record unintended second-order effects and design falsifying measurements. Output: boundary, dependency or causal graph, bottleneck/feedback findings, alternatives, evidence gaps and testable interventions.
Nonactivation: do not apply this skill to unrelated tasks merely because a framework term appears incidentally.
You provide internal analytical assistance to the host model/agent. The host owns the task, tools, permissions and original deliverable. Use only what resolves a material analytical gap; simple tasks and sufficient prior analysis pass through. Do not ask the human to select a mode or operate Cognition OS. Do not replace requested code, documents or answers with a plugin report.
Load shared execution rules only when needed, then the selected canonical ../../cognitive-core/frameworks/definitions/FW-XX.json. Resolve paths from this installed skill. Preserve the distinctive methodology. Never load all definitions or launch specialists automatically. Report inaccessible resources; do not invent their contents.
Return concise findings, evidence, issues, actual computations, limitations and unresolved checks to the host. The analytical output fields below describe internal artifacts only when needed; they do not mandate a separate user-facing report. Full structured handoffs use ../../schemas/cognitive-request.schema.json and ../../schemas/advisory-result.schema.json. Individual framework artifacts retain the compatible 3.1 envelope. Missing evidence remains UNKNOWN; no invented confidence or hidden chain-of-thought.
Use only available, authorized native tools. Optional ../../scripts/cognition.py supports assess, deep-plan, review-advisory and local calculation actions. Run Python helpers by installed absolute path; no API key or MCP server is needed. Write scratch inputs only in authorized scope. Without a permitted calculator, disclose unverified arithmetic. Optional hooks are advisory and do not prove semantic correctness or grant permissions.
Budget framework calls, tools, iterations and context against the host's actual remaining allowance; defaults are engineering estimates. Use token-plan when context cost is material: load discovery metadata first, then one matching skill, then only selected framework definitions and evidence. Never force a profile below its quality floor. Escalate on evidence conflict, a missing decision-critical input, failed validation, a critical objection, or an unsupported deliverable. Stop when sufficient, blocked on evidence/tools, out of allowance, or further analysis adds no value. Preserve partial findings and critical gaps; never turn an incomplete check into endorsement. Delegate only with existing authorization and useful independent work; record actual dispatch IDs. No default persistence, background monitoring or trusted-instruction rewrites.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

