Game Asset Generator
htdt/godogen
Generates game art from text prompts: PNG images, GLB 3D models, rigged characters, animations and sprites, with background removal.
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.
Install Business Docs Sync
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill business-docs-sync -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor business-docs-sync --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/business-docs-sync .claude/skills/business-docs-sync && 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 "business-docs-sync" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/business-docs-sync into .claude/skills/business-docs-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "business-docs-sync", 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/business-docs-syncType 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 business-docs-sync -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor business-docs-sync --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/business-docs-sync .agents/skills/business-docs-sync && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "business-docs-sync" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/business-docs-sync into .agents/skills/business-docs-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "business-docs-sync", 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 business-docs-sync -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor business-docs-sync --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/business-docs-sync .cursor/skills/business-docs-sync && 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 "business-docs-sync" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/business-docs-sync into .cursor/skills/business-docs-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "business-docs-sync", 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/business-docs-sync--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 business-docs-sync -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor business-docs-sync --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/business-docs-sync .gemini/skills/business-docs-sync && 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 "business-docs-sync" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/business-docs-sync into .gemini/skills/business-docs-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "business-docs-sync", 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 business-docs-syncInstalls 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 business-docs-sync -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/business-docs-sync .github/skills/business-docs-sync && 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 "business-docs-sync" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/business-docs-sync into .github/skills/business-docs-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "business-docs-sync", 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 business-docs-sync -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 business-docs-sync --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/business-docs-sync .opencode/skills/business-docs-sync && 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 "business-docs-sync" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/business-docs-sync into .opencode/skills/business-docs-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "business-docs-sync", 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.
Facts
- Skill name
business-docs-sync- GitHub stars
- 380
- Token cost
- ~2.1k tokens
- SKILL.md length
- 767 words
- Files
- 1
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
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.
- Works in 6 steps: Identify What Changed → Update Tier 1 First → Cascade to Tier 2 → …
- Completing a track that changes pricing
- SKILL.md covers When to Use This Skill, The Problem This Solves, Business Document Registry and Sync Trigger Events, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Business Docs Sync is an agent skill from Ibrahim-3d/orchestrator-supaconductor. Use when completing a track that changes pricing, AI models, product features, or asset pipelines — syncs business context documents across all tiers.
Its SKILL.md is about 2.1k 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 Game Development, covering Game assets and audio. 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.
When your agent uses it
- Completing a track that changes pricing
- Product features
- Asset pipelines — syncs business context documents across all tiers
Example prompts
- “/business-docs-sync”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 76c9b10. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Business Docs Sync loads about 2.1k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 767 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from Ibrahim-3d/orchestrator-supaconductor at commit 76c9b10, republished under its AGPL-3.0 licence (© Ibrahim-3d). 767 words, ~2,146 tokens.
Download SKILL.mdSave it as
.claude/skills/business-docs-sync/SKILL.md (or your agent's skills folder).- name
- business-docs-sync
- description
- Use when completing a track that changes pricing, AI models, product features, or asset pipelines — syncs business context documents across all tiers.
Business Document Sync Strategy
Ensures all business strategy, pricing, and product documents stay synchronized when product decisions change during any track execution or evaluation.
When to Use This Skill
- After ANY track completion that changes pricing, model strategy, or business decisions
- After ANY evaluation that produces product decisions or action items
- During
loop-executorStep 3 when a task modifies business-impacting logic - During
loop-execution-evaluatorStep 4 as part of the structural checks - When creating new tracks that depend on business context (pricing, GTM, personas, model strategy)
The Problem This Solves
Projects accumulate business strategy documents across multiple locations:
- Conductor root docs
- Strategy and planning tracks
- Agent skills
- JSON data files (pricing, config)
- Research tracks
When a product decision is made (e.g., adding a new pricing tier, changing the model strategy), these documents become stale unless explicitly synced. The next agent session reads outdated info and makes wrong decisions.
Business Document Registry
Tier 1: Source of Truth (MUST be updated first)
These are the canonical documents. When a decision changes, update these FIRST:
| Document | Location | Contains | Update When |
|---|---|---|---|
| product.md | conductor/product.md | PRD, deliverables, pricing tiers, personas, user stories | Any product feature/pricing change |
| business-strategy.md | conductor/business-strategy.md | GTM, revenue projections, break-even, moat, risk register | Pricing, cost structure, or competitive position changes |
| tech-stack.md | conductor/tech-stack.md | Architecture, model strategy, API integrations, cost projections | Technology decisions, model changes, new integrations |
| Data files | src/data/pricing.json (or equivalent) | UI pricing tiers, features, comparison data | Any pricing change (tiers, features, price points) |
Tier 2: Derived Documents (Update to match Tier 1)
These documents derive from Tier 1 and must stay consistent:
| Document | Location | Derives From | Update When |
|---|---|---|---|
| product-roadmap.md | conductor/product-roadmap.md | product.md, business-strategy.md | Roadmap phases, pricing evolution, or track structure changes |
| product-guidelines.md | conductor/product-guidelines.md | product.md | UI copy, paywall text, pricing display rules |
| prompts.md | conductor/prompts.md | product.md, tech-stack.md | Asset changes, model changes, prompt strategy |
| screen-map.md | conductor/screen-map.md | product.md | New screens, changed user flows |
Tier 3: Skills (Update to match Tier 1 + Tier 2)
Agent skills must reflect current decisions so agents make correct choices:
| Skill | Location | Reflects | Update When |
|---|---|---|---|
| Product knowledge skill | ${CLAUDE_PLUGIN_ROOT}/skills/*/SKILL.md | product.md, pricing model, personas | Product rules, pricing tiers, personas change |
| Integration skills | ${CLAUDE_PLUGIN_ROOT}/skills/*/SKILL.md | tech-stack.md, API docs | SDK patterns, model strategy, cost data, API changes |
Tier 4: Strategy Archives (Reference only — do NOT update)
Historical research outputs capture decisions AT THE TIME they were made and should NOT be retroactively edited.
Exception: If a Tier 4 document is the ONLY place a specific decision is documented, add a "Superseded" note at the top pointing to the updated Tier 1 doc.
Sync Trigger Events
Automatic Triggers (Built into Evaluate-Loop)
| Event | What Triggers | Sync Action |
|---|---|---|
| Track Completion | Any track marked COMPLETE | Run Business Doc Sync Checklist (Step 5.5) |
| Evaluation Complete | Any evaluation with product decisions | Run Business Doc Sync Checklist (Step 5.5) |
| Pricing Change | Price point, tier, or feature list changes | Update Tier 1-3 pricing sections |
| Model Strategy Change | AI model, SDK, or cost structure changes | Update tech-stack.md, skills, cost projections |
| New Package/Tier Added | New pricing tier or product bundle | Update ALL Tier 1-3 pricing sections |
Show full SKILL.md (271 more words)Show less
Manual Triggers
| Trigger | When |
|---|---|
/conductor sync-docs | User explicitly requests doc sync |
| Discovered during planning | Agent notices stale data while reading docs |
Business Doc Sync Checklist
Run this checklist whenever a sync trigger fires. Check each item and update if stale:
## Business Doc Sync Checklist
**Trigger:** [Describe what changed — e.g., "Added new pricing tier"]
**Date:** [YYYY-MM-DD]
### Tier 1: Source of Truth
- [ ] `conductor/product.md` — Pricing section reflects current tiers and features
- [ ] `conductor/business-strategy.md` — Revenue projections use current pricing; cost analysis uses current model costs
- [ ] `conductor/tech-stack.md` — Model strategy, SDK references, and cost projections are current
- [ ] Data files — UI pricing data matches product.md tiers
### Tier 2: Derived Documents
- [ ] `conductor/product-roadmap.md` — Phase pricing and track descriptions are current
- [ ] `conductor/product-guidelines.md` — Paywall copy, pricing display rules match current tiers
- [ ] `conductor/prompts.md` — Prompt strategy aligns with current model capabilities
- [ ] `conductor/screen-map.md` — Screen list includes any new tier-related screens
### Tier 3: Skills
- [ ] Product knowledge skill — Pricing model, tech stack table, personas current
- [ ] Integration skills — SDK patterns, model names, cost data current
### Verification
- [ ] No document references a price point that doesn't match `product.md`
- [ ] No document references a model name that doesn't match `tech-stack.md`
- [ ] No skill references an SDK pattern that doesn't match the actual codebase
- [ ] Data file tier count and features match `product.md` tier count and featuresSync Execution Protocol
Step 1: Identify What Changed
read_file the trigger source (evaluation report, track completion, user instruction) and extract:
- Decision: What was decided?
- Impact: Which documents does this affect?
- Scope: Tier 1 only? Tier 1-2? Tier 1-3?
Step 2: Update Tier 1 First
Always update the source of truth documents first. This prevents cascading inconsistencies.
Step 3: Cascade to Tier 2
Update derived documents to match the new Tier 1 state.
Step 4: Update Tier 3 Skills
Update agent skills so future sessions use correct data.
Step 5: Verify Consistency
Run the sync checklist above and confirm all items pass.
Step 6: Commit
docs: sync business docs — [brief description of what changed]Decision Changelog
Track all product decisions that trigger syncs. This lives in conductor/decision-log.md:
| Date | Decision | Source | Documents Updated | Commit |
|------|----------|--------|-------------------|--------|
| 2026-01-28 | Added premium pricing tier | Track evaluation | product.md, tech-stack.md, business-strategy.md, pricing data, skills | abc1234 |Integration with Evaluate-Loop
This skill integrates into the existing Evaluate-Loop as Step 5.5: Business Doc Sync:
PLAN → EVALUATE PLAN → EXECUTE → EVALUATE EXECUTION
│
PASS → 5.5 BUSINESS DOC SYNC → COMPLETE
FAIL → FIX → re-EXECUTE → re-EVALUATEStep 5.5 runs AFTER evaluation passes but BEFORE marking the track complete. It ensures that any product decisions made during the track are propagated to all documents before the next track begins.
The loop-execution-evaluator checks for business doc staleness as part of its structural checks. If business-impacting changes were made but docs weren't synced, evaluation returns FAIL with a "Business docs out of sync" finding.
Related Documentation
conductor/workflow.md— Evaluate-Loop process (Step 5.5 integration)conductor/decision-log.md— Chronological decision historyconductor/product.md— Tier 1 source of truth (product)conductor/business-strategy.md— Tier 1 source of truth (business)conductor/tech-stack.md— Tier 1 source of truth (technology)
© 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
Files
Just SKILL.md in skills/business-docs-sync of Ibrahim-3d/orchestrator-supaconductor.
Open the folder on GitHubat commit 76c9b10
Compare with similar skills
Business Docs Sync 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 |
|---|---|---|---|---|---|---|
| Business Docs Sync this skillIbrahim-3d/orchestrator-supaconductor | 380 | — | ~2.1k | Automated safety check: Pass | AGPL-3.0 | |
| Game Asset Generatorhtdt/godogen | 7.1k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Threejs 3D Generatorvalkor-ai/loom | 1.2k | 1 repos | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Game Asset AuditDonchitos/Claude-Code-Game-Studios | 26k | — | ~2k | Automated safety check: Pass | MIT | |
| Asset Pipelinerehan-remade/universal-modder | 5.3k | — | ~2k | Automated safety check: Pass | MIT | |
| Game Asset Spec WriterDonchitos/Claude-Code-Game-Studios | 26k | — | ~5k | Automated safety check: Pass | MIT |
Similar skills
Threejs 3D Generator
valkor-ai/loom
Generate, texture, rig, animate, stylize, convert, and download 3D assets for Three.js games via the Tripo API.
Game Asset Audit
Donchitos/Claude-Code-Game-Studios
Audits game assets against naming conventions, file size budgets and format standards, and finds orphaned assets and missing references.
Asset Pipeline
rehan-remade/universal-modder
Turn generated or hand-made art into exactly what a game engine loads.
Game Asset Spec Writer
Donchitos/Claude-Code-Game-Studios
Writes per-asset visual specs and AI image-generation prompts for a game's characters, enemies and screens, driven by the GDD, art bible and an entity inventory.
2D Sprite Generator
0x0funky/agent-sprite-forge
Produces game-ready 2D characters, creatures, props, icons and effects as master stills, sheets or clips, and exports frames for common game engines.
More from Ibrahim-3d/orchestrator-supaconductor
All 27 skills in this repoCto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Context Driven Development
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…
Agent Factory
Ibrahim-3d/orchestrator-supaconductor
Creates specialized worker agents dynamically from templates.
Board Of Directors
Ibrahim-3d/orchestrator-supaconductor
Simulate a 5-member expert board deliberation for major decisions.
Context Loader
Ibrahim-3d/orchestrator-supaconductor
Load project context efficiently for Conductor workflows. An agent skill from Ibrahim-3d/orchestrator-supaconductor.
Eval Business Logic
Ibrahim-3d/orchestrator-supaconductor
Specialized business logic evaluator for the Evaluate-Loop. An agent skill from Ibrahim-3d/orchestrator-supaconductor.
Related
Categories
Questions about Business Docs Sync
What does Business Docs Sync do?
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. Business Docs Sync is an agent skill from Ibrahim-3d/orchestrator-supaconductor. Use when completing a track that changes pricing, AI models, product features, or asset pipelines — syncs business context documents across all tiers.
When should I use Business Docs Sync?
Business Docs Sync fits situations like: completing a track that changes pricing; product features; asset pipelines — syncs business context documents across all tiers.
How do I install Business Docs Sync in Claude Code?
Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill business-docs-sync -a claude-code`. Or copy the skill folder (skills/business-docs-sync in Ibrahim-3d/orchestrator-supaconductor) into .claude/skills/business-docs-sync in your project. Claude Code loads it when a task matches its description.
How do I install Business Docs Sync in Codex?
Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill business-docs-sync -a codex`. Or copy the skill folder (skills/business-docs-sync in Ibrahim-3d/orchestrator-supaconductor) into .agents/skills/business-docs-sync in your project. Codex loads it when a task matches its description.
Can I use Business Docs Sync in Cursor, Gemini CLI or GitHub Copilot?
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 business-docs-sync -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/business-docs-sync, .gemini/skills/business-docs-sync, .github/skills/business-docs-sync and .opencode/skills/business-docs-sync in your project.
What does Business Docs Sync need to run?
SKILL.md names no scripts, command-line tools or credentials: Business Docs Sync is instructions for the agent only.
Does Business Docs Sync access the network?
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.
Is Business Docs Sync safe to install?
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.
What licence does Business Docs Sync use?
Business Docs Sync 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.
How many tokens does Business Docs Sync use?
About 2.1k tokens (SKILL.md is roughly 8.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Business Docs Sync?
Skills that share tags, products or a category with Business Docs Sync: Game Asset Generator (htdt/godogen, 7.1k stars), Threejs 3D Generator (valkor-ai/loom, 1.2k stars), Game Asset Audit (Donchitos/Claude-Code-Game-Studios, 26k stars) and Asset Pipeline (rehan-remade/universal-modder, 5.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Business Docs Sync?
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.