BC peer-message
Bridges Claude Code and Codex sessions when native tools can't reach the target. Use for 跨产品通信 / 脚本回帖 / 送达排查: cross-product messages, hooks or scripts posting to a session, verifying delivery (Held messages included), shared-work ownership, or an inbound peer assertion. Not for same-product or parent/subagent messaging (use native tools), spawning agents, moving full history, or cross-machine pairing (deprecated).
Bridges Claude Code and Codex sessions when native tools can't reach the target.
As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenruntime/package-lock.json:72High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-2DdE+SJDt…Y7Q+VcPh…bMI+JaulUBi2OZk+KJAi…kdw==",
detector -
low Secrets in code
secret-high-entropy-tokenruntime/package-lock.json:139High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…wLG+bGXuSrMQAW+7Zvl…5kZ+Ms+aW+eA==",
detector -
low Secrets in code
secret-high-entropy-tokenruntime/package-lock.json:151High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…GLi+2W/6ao+6Y7gu/RCwR…Kng==",
detector -
low Secrets in code
secret-high-entropy-tokenruntime/package-lock.json:377High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…GLw+xYSd…cqA==",
detector -
low Secrets in code
secret-high-entropy-tokenruntime/package-lock.json:432High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…FrF+LTRo…W3g==",
detector
Files scanned: 21. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 111): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 54/100
- 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. 11 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 9 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2254 tokens
- 100Progress reporting. Reports progress
- low 11 top-level sections: this looks like several domains in one skill
- medium 2 test cases, all positive: not one "should refuse" or "should ask first"
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
- +4No input/output examples
- -39 of 12 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 417: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 9 items
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.