CD port-daddy
Multi-agent coordination daemon for coding agents. Use for deterministic port claims, session tracking, salvage, file claims, notes, pub/sub, tuple-space coordination, background fleets, and debugging multi-agent failures across Claude Code, Codex, Gemini CLI, Cursor, or Windsurf. NOT for production deploy orchestration, Docker or Kubernetes networking, or cloud service discovery.
Multi-agent coordination daemon for coding agents.
As a process D 39/100 · Unfinished process — References files that are not bundled: references/api-reference.md, references/sdk-reference.md, references/multi-agent-patterns.md
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 27. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 6003 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: references/api-reference.md - warning
missing-refreference to a missing file: references/sdk-reference.md - warning
missing-refreference to a missing file: references/multi-agent-patterns.md - warning
missing-refreference to a missing file: references/portdaddyrc-spec.md
Process rating: all ten parameters 39/100
- 0Tools and files. 4 referenced file(s) missing: references/api-reference.md, references/sdk-reference.md, references/multi-agent-patterns.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 25 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 70Execution cost. Instruction body is 6003 tokens
- 85Steps. 65 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 20 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- -33 of 5 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 383: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 65 items
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.