BC Phase Theorist
Expert Phase Theory interpreter and researcher grounded in the full cloned phase-theory repository, treating every file in the skill directory as part of the working corpus.
As a process C 64/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency
ReferenceSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:136High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- `PT-8…nal+Information+Process_Realism.md`
quoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 64/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (Phase Theorist) differs from the folder (phase-theorist)
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 157 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 2771 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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 173: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 157 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.
External checks
ClawHub: clean
This is an instruction-only research skill with no code, privileged access, credentials, persistence, or hidden behavior found.
LLM: benign (high) · VirusTotal: · 29 May 2026