team-quality-ledger
Skill1 starsChanged 5 months agoNo licenceView on GitHub
팀 오케스트레이터(팀장)가 *자율 할당한 작업의 품질을 추적*하고, *2회 연속 부적절 시 전문화 워커 생성 신호*를 띄워야 할 때 사용한다. 구체적으로: 품질을 직접 판정하지 않는다(판정은 검증팀 review-gate가 정본). 이 스킬은 *verdict를…
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/agents/agents.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- agent-clone-setupSkill
- create-team-agentSkill
- give-feedbackSkill
- process-feedbackSkill
- register-termSkill
- reminders-team-bridgeSkill
- set-team-goalSkill
- team-derive-authorSkill
- team-inboxSkill
- team-initSkill
- write-skillSkill
- write-subagentSkill
- write-taskSkill
The file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

