BC lobsterops
AI Agent Observability & Debug Console - flight recorder and debug console for autonomous AI systems
As a process C 50/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
ProcedureSupabaseSoftware developmentInfrastructureAI and agentstype 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 · 6
✓ No critical or high findings
Medium and low: 6
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:282High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"integrity": "sha5…ywo+qwL+oL8H…C1U+vRfLQDvw==",
quoted -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:298High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-Yqfm+XDx0+Prh3…1yC+JWZ2…IL7+vK+Clp7…D7g==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:311High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…xZl+RoGR…fbT/ZgrF…0EA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:324High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…3bJ+V0If…IXN+CL65…a4w==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:340High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"integrity": "sha5…H47+FFon…OsV/4+RRsz…0ig==",
quoted -
low Secrets in code
secret-password-literalsrc/core/PIIFilter.js:27Hard-coded password / key literal (may be an example)apiKey: /(?:sk|pk|key|token|api[_-]?key|bearer)[-_]?(?:[a-zA-Z0-9][-_]?){20,}/gi,
Files scanned: 22. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 50/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 100Steps. 16 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 865 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 100: 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: 16 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.
External checks
ClawHub: clean
LobsterOps is a coherent agent observability tool, but users should treat its logs as sensitive because they can include prompts, reasoning, tool inputs, outputs, and errors.
LLM: benign (high) · VirusTotal: · 29 May 2026