Tech brief orchestrator
Skill harryl6798/vc-diligence-skill/skills/tech-brief-orchestrator
npx -y skills add harryl6798/vc-diligence-skill --skill tech-brief-orchestratorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 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
High-level technical "Editor-in-Chief" that coordinates specialized sub-agents to produce exhaustive, research-grade technical briefs.
SKILL.md
2.2 KB, 500 tokens by cl100k_base, as published. Nobody here has run it
Technical Brief Orchestrator: The Master System Architect (V2)
This skill coordinates hyper-depth technical audits. It is optimized for Educational Deep-Dives, moving beyond factual lists into causal, step-by-step explanations of infrastructure.
1. THE "EDUCATIONAL MASTER" MANDATE
The goal is a document that a Lead Partner can use to understand the technology from first principles.
- The Causality Rule: Every technical component must be explained through its inputs, its mathematical transformation, and its specific clinical output.
- The "How it Works" Step-by-Step: Every section MUST include a numbered walkthrough of the data journey.
- Mental Model Anchoring: Use the "Complexity Explanation" blocks to ground abstract math in physical analogies.
2. THE ORCHESTRATION WORKFLOW
2.1 Phase 1: Mechanics Harvesting
For every pillar, the Orchestrator MUST identify the Functional Steps:
- Search for "How [Component X] works step by step."
- Extract the specific mathematical transformations (e.g., "Encoder projects to 32k dimensions, then ReLU gating...").
- Store these in
raw_findings/tech/mechanics_[pillar_name].md.
2.2 Phase 2: Specialized Process Teardowns
Activate sub-agents with the instruction to write a Functional Anatomy of their pillar:
- Superposition Auditor: Explain the "Superposition Problem" as a geometric data-jumble.
- SAE-Rad Factory: Detail the "Disentanglement Assembly Line."
- Causal Probe Specialist: Detail the "Counterfactual Verification Loop."
- LookOut Trajectory Analyst: Detail the "Path Forecasting Logic."
- Mecha Infrastructure Expert: Detail the "Footprint Optimization Process."
2.3 Phase 3: Recursive Deepening
Scan for any "Then a miracle occurs" jumps in logic. If a process step is missing (e.g., "How does the feature get its name?"), reissue searches to find the specific primitive.
2.4 Phase 4: Master Assembly (The Learning Doc)
Assemble master_technical_brief.md as a cohesive Technical Guidebook.
End of Technical Brief Orchestrator Skill.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.