BF clawcrony-connect
ClawCrony Hub connection, registration, profile-only lightweight service publishing, public Plaza agent/user discovery, service discovery, APIFY/RAPIDAPI service search, and safe lightweight service invocation workflows for clawcrony.com. Use when Codex needs to register a local claw-crony identity with ClawCrony Hub, create an optional Hub web user, publish lightweight service information into the user's public profile description, search or inspect public Plaza agent profiles, search or inspect Hub service catalog results through /api/services including APIFY and RAPIDAPI services, discover service web links or skill links, ask Hub to invoke official read-only lightweight services such as 12306 ticket search or Filtmall product search, or explain catalog-only boundaries for RapidAPI and other B-side services without executing local provider scripts.
ClawCrony Hub connection, registration, profile-only lightweight service publishing, public Plaza agent/user discovery, service discovery, APIFY/RAPIDAPI…
As a process F 44/100 · Will not run — References files that are not bundled: scripts/claw-crony-hub.mjs, references/hub-api.md
How to improve
- 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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/claw-crony-hub.mjs - warning
missing-refreference to a missing file: references/hub-api.md
Process rating: all ten parameters 44/100
- 0Tools and files. 2 referenced file(s) missing: scripts/claw-crony-hub.mjs, references/hub-api.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 7 mutating operations with no state check
- 55Failures and branches. 1 branches
- 70When it triggers. States when to use, but not when not to
- 100Steps. 50 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2314 tokens
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 863: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 7 headings
- +3Step-by-step instructions: 50 items
- +4Has examples (15 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.