framework-composer
Skill3 starsChanged 24 days agoApache-2.0View on GitHub
Select, order or run specific Cognition OS mental models and check workflow dependencies and handoffs.
In this repository11 other files it gives its agents.
- adversarial-reviewSkill
- artifact-qualitySkill
- case-intelligenceSkill
- cognition-orchestratorSkill
- cognitive-masterySkill
- executive-synthesisSkill
- quantitative-decisionSkill
- root-cause-analysisSkill
- setupSkill
- strategic-decisionSkill
- systems-analysisSkill
The file
Files
Framework Composer
Required: problem or explicit model selection. Optional: requested order, constraints and mode.
Use the compact registry index to resolve names and stable IDs. Load each chosen definition on demand. All 50 models are accessible here; there are no generic replacement frameworks. Request clarification for an unrecognized model rather than inventing a new source ID. CUSTOM supports up to 12 steps per bounded workflow; split longer work into explicit phases. Use analysis-plan to validate dependencies and produce execution waves. Steps in one wave may run concurrently only when the host exposes native delegation and the authorized concurrency allowance is greater than one; otherwise follow the sequential fallback.
For each transition map actual upstream fields to the next required inputs and explain semantic fit. Mark incompatible or absent inputs BLOCKED and ask for the minimum missing context. Validate ordering and DAG dependencies before starting. Preserve user-selected order unless a missing prerequisite requires a disclosed change. Conditional branches run only when their stated evidence condition holds.
Output: framework IDs and order, dependencies, input mappings, missing inputs, stopping rule, then the requested framework-specific analytical payloads.
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.

