.claude/skills/glm5/SKILL.md
GLM-5 Agent Teams skill for spawning teammates with thinking mode
npx skillsauth add alfredolopez80/multi-agent-ralph-loop glm5Install this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Spawn GLM-5 powered teammates with native thinking mode.
# Spawn single teammate
/glm5 coder "Implement auth"
# Spawn for review
/glm5 reviewer "Review this code"
# Spawn for testing
/glm5 tester "Generate tests"
This skill integrates with:
/orchestrator - GLM-5 as teammate option/parallel - GLM-5 for parallel review/iterate - GLM-5 for iterative tasks| Type | Role | Best For |
|------|------|----------|
| coder | Implementation | Features, refactoring, bugs |
| reviewer | Code Review | Security, quality, patterns |
| tester | Test Generation | Unit tests, coverage |
| planner | Architecture | Design, planning |
| researcher | Documentation | Docs, exploration |
When this skill is invoked:
$ARGUMENTStask-{timestamp}.claude/scripts/glm5-teammate.sh <role> "<task>" "<task_id>"
cat .ralph/team-status.json
tail -f .ralph/logs/teammates.log
| File | Content |
|------|---------|
| .ralph/teammates/{id}/status.json | Task status & metadata |
| .ralph/reasoning/{id}.txt | GLM-5 reasoning |
| .ralph/logs/teammates.log | Activity log |
User: /glm5 coder "Implement factorial in TypeScript"
[GLM-5 thinking...]
Reasoning: The user wants a TypeScript factorial function...
Output: function factorial(n: number): number { ... }
✅ Task completed
📁 Status: .ralph/teammates/task-123/status.json
🧠 Reasoning: .ralph/reasoning/task-123.txt
development
Living knowledge base management. Actions: search (query vault), save (store learning), index (update indices), compile (raw->wiki->rules graduation), init (create vault structure). Follows Karpathy pipeline: ingest->compile->query. Use when: (1) searching accumulated knowledge, (2) saving learnings, (3) compiling raw notes into wiki, (4) initializing a new vault. Triggers: /vault, 'vault search', 'knowledge base', 'save learning'.
testing
Produce a verifiable technical specification before coding. 6 mandatory sections: Interfaces, Behaviors, Invariants (from Aristotle Phase 2), File Plan, Test Plan, Exit Criteria (executable bash commands + expected results). Use when: (1) before implementing features with complexity > 4, (2) as Step 1.5 in orchestrator workflow, (3) when requirements need formalization. Triggers: /spec, 'create spec', 'write specification', 'technical spec'.
testing
Pre-launch shipping checklist orchestrating /gates, /security, /browser-test, /perf. Ensures nothing ships without passing all quality checks. Use when: (1) before deploying, (2) before merging to main, (3) before release. Triggers: /ship, 'ship it', 'ready to deploy', 'pre-launch check'.
development
Performance optimization skill. Core Web Vitals via Lighthouse, bundle size analysis, metrics tracking over time. Use when: (1) optimizing frontend performance, (2) analyzing bundle size, (3) tracking metrics regression. Triggers: /perf, 'performance audit', 'core web vitals', 'bundle size'.