skill-synthesis
Compose multiple installed skills into one coordinated execution stack with ordered packets, minimal context load, and deterministic handoff artifacts. Use when tasks span multiple domains (for example HYDRA + browser + training + deploy) and you need a single combined workflow instead of invoking skills one-by-one.
Best use case
skill-synthesis is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Compose multiple installed skills into one coordinated execution stack with ordered packets, minimal context load, and deterministic handoff artifacts. Use when tasks span multiple domains (for example HYDRA + browser + training + deploy) and you need a single combined workflow instead of invoking skills one-by-one.
Teams using skill-synthesis should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/skill-synthesis/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How skill-synthesis Compares
| Feature / Agent | skill-synthesis | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Compose multiple installed skills into one coordinated execution stack with ordered packets, minimal context load, and deterministic handoff artifacts. Use when tasks span multiple domains (for example HYDRA + browser + training + deploy) and you need a single combined workflow instead of invoking skills one-by-one.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Skill Synthesis ## Overview Use this skill to fuse multiple installed skills into one execution loop with clear ordering, packet boundaries, and artifacts. ## Quick Start 1. Build a stack from a task prompt. ```powershell python C:\Users\issda\.codex\skills\skill-synthesis\scripts\compose_skill_stack.py --task "Build gamma funnels and deploy" --top 8 ``` 2. Run the resulting packets in order from highest leverage to lowest risk. ## Workflow ### 1) Select Minimal Stack - Pick one **primary** skill (owns outcome). - Pick up to four **support** skills (execution lanes). - Do not load the whole skill catalog unless explicitly requested. ### 2) Build Ordered Packets - Packet A: discovery/research - Packet B: implementation - Packet C: validation/smoke - Packet D: publish/deploy - Packet E: evidence + vault notes ### 3) Execute with Context Discipline - Keep live context to only the active packet. - Move long notes to artifacts or vault docs. - Keep source links and proofs in packet output. ### 4) Output Contract - stack plan JSON - ordered packet list - execution report (what ran, what passed, what is blocked) ## Built-in Stack Profiles ### `hydra-library-wing` - `hydra-agent-relay-synthesis` - `aetherbrowser-arxiv-nav` - `aetherbrowser-github-nav` - `hugging-face-model-trainer` - `notion` Use for deep research + dataset handoff + multi-agent synthesis. ### `revenue-gamma-funnel` - `living-codex-browser-builder` - `article-posting-ops` - `scbe-shopify-money-flow` - `aetherbrowser-shopify-nav` - `vercel-deploy` Use for landing pages, conversion flow, and web deployment. ### `platform-release` - `development-flow-loop` - `playwright` - `scbe-connector-health-check` - `vercel-deploy` Use for implementation -> smoke -> deploy. ## Rules - Favor official docs and primary sources for unstable facts. - Keep stack size small unless user explicitly asks for full-spectrum mode. - Prefer deterministic scripts and repeatable packets over ad-hoc chat instructions. - Record evidence paths for every packet. ## Resources ### scripts/ - `compose_skill_stack.py`: Generate ranked skill stacks and packet plans from a task description. ### references/ - `stack-profiles.md`: Reusable profile templates and packet recipes.
Related Skills
scbe-universal-synthesis
Orchestrate all installed Codex skills through an auto-updating synthesis matrix with Sacred Tongues routing, emotion/intent metadata, and decodable lexicon packets tied to established SCBE characters. Use when the user asks for cross-skill coordination, auto skill updates, multi-skill routing, or Sacred Tongues intent mapping.
scbe-internet-workflow-synthesis
Synthesize and operate SCBE end-to-end internet workflows by discovering local and GitHub architecture templates, generating a baseline web pipeline profile, running ingestion and governance scans, and tuning system variables after the first run. Use when users ask to build, repair, or optimize internet workflow pipelines, workflow architecture maps, n8n or agent orchestration flows, or post-baseline threshold and concurrency tuning.
scbe-training-pair-authoring
Create prompt and response and metadata training pairs from SCBE documents, repair traces, terminal sessions, and operational workflows using the repository's canonical dataset contract and provenance rules.
scbe-spin-conversation-engine
Generate SFT training data via radial matrix conversation pivots with D&D-style combat research mode. Produces diverse, cost-effective training pairs with Sacred Tongue encoding, golden spiral problem distribution, and harmonic re-attunement.
scbe-research-training-bridge
Stage arXiv evidence and Obsidian markdown into source-grounded Hugging Face training bundles for research, review, and later SFT runs.
scbe-document-management
Consolidate overlapping docs, classify files by authority, and keep SCBE repo documents aligned with runtime truth. Use when the repo has drift between canonical docs, public docs, proposal notes, research branches, and generated evidence.
scbe-colab-bridge
Control Google Colab notebooks from Claude Code via Chrome extension. Execute cells, run terminal commands, read outputs, and manage GPU compute remotely.
scbe-claim-to-code-evidence
Map SCBE Notion technical claims, proof pages, and patent-facing architecture notes to concrete repository evidence such as code paths, tests, demos, and docs. Use when Codex needs to build a due-diligence packet, claim-to-code audit, implementation crosswalk, patent support note, or proof summary from local Notion exports and repo artifacts.
scbe-autonomous-worker-productizer
Turn SCBE automation, autonomous worker, and revenue-system notes into concrete offers, workflow packs, pilot plans, or SaaS-facing product packets. Use when Codex needs to package Notion automation pages into buyer-ready offerings, n8n/Zapier workflow designs, flock-backed worker systems, or implementation roadmaps tied to existing SCBE repo surfaces.
multi-agent-cloud-offload
Deterministically sort, bundle, verify, and offshore local files through multiple AI/model lanes while capturing training rows and method evidence. Use when Codex needs to inventory folders, batch-process files, upload them to cloud targets such as rclone-backed Google Drive, Hugging Face, or GitHub, and only delete sources after the configured number of verified targets succeed.
long-form-work-orchestrator
Run long-form engineering work in checkpointed phases with deterministic artifacts, resilience handling, and end-of-run reliability reporting.
scbe-code-scanning-ops
Operate GitHub code scanning and CodeQL remediation for SCBE repositories. Use when triaging code-scanning alerts, mapping alert classes to fix patterns, validating targeted regressions, or wiring dedicated CodeQL workflows and runbooks into the repo.