Loading the registry…
Set up a complete agent team with file-based planning for complex multi-agent projects. Use when: (1) user asks to start a new complex project with a team/swarm, (2) user says "set up team", "create team", "build a team for X", "start project X", (3) user invokes /CCteam-creator with a project name, (4) user wants to organize a multi-phase project with parallel agent workers and persistent progress tracking. Creates TeamCreate, planning files (.plans/project/), per-agent work directories, and spawns configured teammates. TRIGGER on: "team", "swarm", "start project", "set up project", "create team for", "build team", "organize project", "multi-agent project". IMPORTANT: You (team-lead) MUST read all reference files directly — do NOT delegate to subagents. NOTE: After initial setup, you can add new teammates at any time — just spawn a new Agent with the team_name and follow the same onboarding pattern. The team is not locked after creation.
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'jessepwj/ccteam-creator (CCteam-creator)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'jessepwj/ccteam-creator (CCteam-creator)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
15 findings · 9.9s
v0.3.74
3 findings · 1.6s
v0.1.0
0 findings · 4.3s
v0.1.0
0 findings · 4.3s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.2s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image, nerlo-multi-source.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 16, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicable | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 18 findings above stand exactly as their scanners reported them, at full severity.