AD basecamp-cli
Manage Basecamp (via bc3 API / 37signals Launchpad) projects, to-dos, messages, and campfires via a TypeScript CLI. Use when you want to list/create/update Basecamp projects and todos from the terminal, or when integrating Basecamp automation into Clawdbot workflows.
As a process D 47/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:34High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…nS4+204nGb1RiX/WXYH…II9/e2DW…VvQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:44High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-GZMB+a0mO…4cw+w1WV…UED+1X8a…sJi+8mgpw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:214High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…HK5+NE/tvnRLbIqUWa+0E9N4WNMjmp/kXXP…R8w==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:435High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…78O/B3Kkh+nKABUF++bvJv…56W+C8F9…X6m+IktJnIb1Jjg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:559High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…CWe+uc7w…CUH+Q6cH…06w==",
detector
Files scanned: 17. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 47/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 75Steps. 3 steps
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 145 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)
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 267: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 3 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.