Claude Code Skill
codeaashu/claude-code
Development conventions and architecture guide for the Claude Code CLI repository.
Technical implementation consultation for Conductor orchestrator.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill tech-lead -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor tech-lead --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/leads/tech-lead .claude/skills/tech-lead && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "tech-lead" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/tech-lead into .claude/skills/tech-lead/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-lead", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/tech-leadType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill tech-lead -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor tech-lead --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/leads/tech-lead .agents/skills/tech-lead && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tech-lead" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/tech-lead into .agents/skills/tech-lead/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-lead", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill tech-lead -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor tech-lead --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/leads/tech-lead .cursor/skills/tech-lead && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "tech-lead" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/tech-lead into .cursor/skills/tech-lead/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-lead", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Ibrahim-3d/orchestrator-supaconductor.git --path skills/leads/tech-lead--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill tech-lead -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor tech-lead --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/leads/tech-lead .gemini/skills/tech-lead && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "tech-lead" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/tech-lead into .gemini/skills/tech-lead/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-lead", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor tech-leadInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill tech-lead -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/leads/tech-lead .github/skills/tech-lead && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "tech-lead" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/tech-lead into .github/skills/tech-lead/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-lead", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill tech-lead -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor tech-lead --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/leads/tech-lead .opencode/skills/tech-lead && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "tech-lead" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/leads/tech-lead into .opencode/skills/tech-lead/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-lead", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
tech-leadTechnical implementation consultation for Conductor orchestrator.
Tech Lead is an agent skill from Ibrahim-3d/orchestrator-supaconductor. Technical implementation consultation for Conductor orchestrator. Advises on implementation approach, dependency choices, and coding patterns. Can approve dependencies under size threshold. Escalates large dependencies or breaking tooling changes to Board of Directors.
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: Multi-agent orchestration system for Claude Code with parallel execution, automated quality gates, Board of Directors, and bundled Superpowers skills. The licence is AGPL-3.0.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 76c9b10. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are json and typescript).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Tech Lead loads about 2.2k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 529 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from Ibrahim-3d/orchestrator-supaconductor at commit 76c9b10, republished under its AGPL-3.0 licence (© Ibrahim-3d). 529 words, ~2,210 tokens.
.claude/skills/tech-lead/SKILL.md (or your agent's skills folder).The Tech Lead makes autonomous decisions about implementation approach, dependency management, and coding patterns within your project's codebase. Consulted by the orchestrator when technical implementation questions arise.
| Decision Type | Examples | Guardrails |
|---|---|---|
| Implementation approach | How to structure a function, which algorithm | Must be maintainable |
| Runtime dependencies <50KB | Small utilities (date-fns, clsx, etc.) | Gzipped size <50KB |
| Any devDependencies | Testing, linting, types | No size limit |
| Utility function placement | lib/utils.ts vs feature/helpers.ts | Follow conventions |
| Type definitions | Interface design, type helpers | TypeScript best practices |
| Hook composition | Custom hook structure | React patterns |
| Test file organization | Co-location vs tests | Follow existing pattern |
| Refactoring for clarity | Rename, extract, simplify | No behavior change |
| Code style within patterns | Formatting, naming | Match codebase |
"agentic" mode: Escalate to Board. "human-in-the-loop" mode: Escalate to user.
| Decision Type | Reason |
|---|---|
| Runtime dependencies >50KB | Bundle size impact |
| Remove dependencies | Could break features |
| Major version upgrades | Breaking changes risk |
| Build configuration changes | Could break CI/CD |
| Deployment configuration | Infrastructure impact |
| Database migration complexity | Data risk |
| Performance tradeoffs with user impact | UX decision |
The 50KB threshold is for gzipped bundle size. Use bundlephobia.com to check:
Under 50KB (Can Approve):
date-fns - 8KB (tree-shakeable)clsx - 0.5KBzustand - 2KBreact-hook-form - 9KBzod - 14KBlodash-es (individual imports) - variesOver 50KB (Escalate):
moment - 67KBlodash (full) - 71KBchart.js - 65KBthree.js - 150KB@mui/material - varies but heavyWhen consulted, the Tech Lead follows this process:
{
"lead": "tech",
"decision_made": true,
"decision": "Use date-fns for date formatting",
"reasoning": "8KB gzipped, under 50KB threshold. Tree-shakeable so only imports what's used. Immutable API matches our patterns.",
"dependency_size": "8KB gzipped",
"alternatives_considered": ["Intl.DateTimeFormat (native but verbose)", "dayjs (similar but less maintained)"],
"implementation_note": "Import specific functions: import { format, parseISO } from 'date-fns'",
"escalate_to": null,
"escalation_reason": null
}{
"lead": "tech",
"decision_made": false,
"decision": null,
"reasoning": "Dependency exceeds 50KB threshold",
"dependency_size": "67KB gzipped",
"alternatives_considered": ["date-fns (8KB)", "dayjs (2KB)", "native Intl API"],
"escalate_to": "board",
"escalation_reason": "moment.js is 67KB gzipped, exceeding 50KB threshold. Recommend date-fns (8KB) as alternative. Please confirm if moment is required for specific features."
}When making decisions, consult:
package.json — Current dependenciesconductor/tech-stack.md — Technology decisionsCheck your project's tech-stack.md for the established technology decisions. Common stacks include:
Question: "Should we use a library for form validation?"
Process:
Decision:
{
"lead": "tech",
"decision_made": true,
"decision": "Use zod for schema validation with react-hook-form for form state",
"reasoning": "zod (14KB) + react-hook-form (9KB) = 23KB total, well under threshold. Both widely adopted, TypeScript-first, work well together.",
"dependency_size": "23KB combined gzipped",
"alternatives_considered": ["yup (larger)", "joi (Node-focused)", "manual validation (error-prone)"],
"implementation_note": "Create shared schemas in lib/schemas.ts, use zodResolver with useForm",
"escalate_to": null
}Question: "Should we add Chart.js for analytics dashboard?"
Process:
Decision:
{
"lead": "tech",
"decision_made": false,
"decision": null,
"reasoning": "Chart.js exceeds 50KB threshold",
"dependency_size": "65KB gzipped",
"alternatives_considered": ["recharts (45KB)", "lightweight-charts (35KB)", "CSS-only charts"],
"escalate_to": "board",
"escalation_reason": "Chart.js is 65KB gzipped. Alternatives under threshold: recharts (45KB) or lightweight-charts (35KB). If full Chart.js features needed, please confirm."
}Question: "How should I structure the API response transformation?"
Process:
Decision:
{
"lead": "tech",
"decision_made": true,
"decision": "Create a transformer function in lib/api/transforms.ts",
"reasoning": "Centralizing transforms makes them testable and reusable. Keeps API route handlers thin.",
"implementation_note": "Export typed transform functions: transformResponse(raw: RawType): CleanType",
"escalate_to": null
}Question: "Can we add prettier-plugin-tailwindcss?"
Process:
Decision:
{
"lead": "tech",
"decision_made": true,
"decision": "Add prettier-plugin-tailwindcss as devDependency",
"reasoning": "DevDependencies have no bundle size impact. This plugin auto-sorts Tailwind classes, improving consistency.",
"dependency_size": "N/A (devDependency)",
"implementation_note": "Add to .prettierrc: plugins: ['prettier-plugin-tailwindcss']",
"escalate_to": null
}Question: "Should we upgrade from Next.js 14 to Next.js 15?"
Process:
Decision:
{
"lead": "tech",
"decision_made": false,
"decision": null,
"reasoning": "Major version upgrades can have breaking changes",
"escalate_to": "board",
"escalation_reason": "Next.js 15 is a major version upgrade from 14. This may involve breaking changes to routing, middleware, or APIs. Recommend reviewing Next.js 15 migration guide before proceeding. Please confirm if upgrade should proceed."
}The orchestrator invokes this lead when encountering technical questions:
// Orchestrator consults tech lead
const response = await consultLead("tech", {
question: "Which date formatting library should we use?",
context: {
track_id: "feature-track-id",
current_task: "Task 3: Format timestamps in UI",
current_dependencies: ["zustand", "tailwindcss"]
}
});
if (response.decision_made) {
// Log consultation and proceed
metadata.lead_consultations.push(response);
proceed(response.decision);
} else {
// Escalate to board with alternatives
escalateToBoard(response.escalation_reason);
}© Ibrahim-3d, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/leads/tech-lead of Ibrahim-3d/orchestrator-supaconductor.
Open the folder on GitHubat commit 76c9b10
Tech Lead next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Tech Lead this skillIbrahim-3d/orchestrator-supaconductor | 380 | — | ~2.2k | Automated safety check: Pass | AGPL-3.0 | |
| Claude Code Skillcodeaashu/claude-code | 3.4k | 1 repos | ~2.7k | Automated safety check: Pass | Proprietary | |
| Gearcoleco Debuggingdrhelius/Gearcoleco | 141 | — | ~3.5k | Automated safety check: Pass | GPL-3.0 | |
| Tutti Agent Workspace Apptutti-os/tutti | 3.8k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Helmor Debug Loopdohooo/helmor | 1.3k | — | ~917 | Automated safety check: Pass | Apache-2.0 | |
| Migrate To Svelterazorpay/blade | 656 | — | ~4.7k | Automated safety check: Pass | MIT |
codeaashu/claude-code
Development conventions and architecture guide for the Claude Code CLI repository.
drhelius/Gearcoleco
Debug and trace ColecoVision and Super Game Module games using the Gearcoleco emulator MCP server.
tutti-os/tutti
Build or evolve a complex agent-enabled Tutti workspace app repository.
dohooo/helmor
Autonomous local-development debugging loop for Helmor bugs.
razorpay/blade
Orchestrate parallel migration of Blade React components to Svelte 5.
tjx666/vscode-mcp
TypeScript code style and repo conventions for VSCode MCP — inference vs explicit types, ESM import suffixes, zod schema contracts, async VSCode/Node APIs, JSON-safe IPC results, JSDoc for public…
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…
Ibrahim-3d/orchestrator-supaconductor
Creates specialized worker agents dynamically from templates.
Ibrahim-3d/orchestrator-supaconductor
Simulate a 5-member expert board deliberation for major decisions.
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when completing a track that changes pricing, AI models, product features, or asset pipelines — syncs business context documents across all tiers.
Ibrahim-3d/orchestrator-supaconductor
Load project context efficiently for Conductor workflows. An agent skill from Ibrahim-3d/orchestrator-supaconductor.
Technical implementation consultation for Conductor orchestrator. Tech Lead is an agent skill from Ibrahim-3d/orchestrator-supaconductor. Technical implementation consultation for Conductor orchestrator.
Tech Lead fits situations like: development work in your project.
Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill tech-lead -a claude-code`. Or copy the skill folder (skills/leads/tech-lead in Ibrahim-3d/orchestrator-supaconductor) into .claude/skills/tech-lead in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill tech-lead -a codex`. Or copy the skill folder (skills/leads/tech-lead in Ibrahim-3d/orchestrator-supaconductor) into .agents/skills/tech-lead in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill tech-lead -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tech-lead, .gemini/skills/tech-lead, .github/skills/tech-lead and .opencode/skills/tech-lead in your project.
SKILL.md names no scripts, command-line tools or credentials: Tech Lead is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Tech Lead is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.2k tokens (SKILL.md is roughly 8.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Tech Lead: Claude Code Skill (codeaashu/claude-code, 3.4k stars), Gearcoleco Debugging (drhelius/Gearcoleco, 141 stars), Tutti Agent Workspace App (tutti-os/tutti, 3.8k stars) and Helmor Debug Loop (dohooo/helmor, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Ibrahim-3d (a GitHub user) maintains it in Ibrahim-3d/orchestrator-supaconductor, which has 380 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on September 27, 2026.
Source: Ibrahim-3d/orchestrator-supaconductor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.