BD byagent
Use when writing, designing, or turning anything into a shareable page: a Markdown document (report, plan, notes, spec, analysis, write-up, README) or an HTML artifact (dashboard, tool, landing page, visualization), including Claude-style artifacts. Markdown files publish directly and are rendered into a styled page. Use it after producing any document, report, plan, analysis, spec, or table that is likely to be reused or shared. Also use for "publish this", "give me a link", agent artifacts, or comments on a published page.
Use when writing, designing, or turning anything into a shareable page: a Markdown document (report, plan, notes, spec, analysis, write-up, README) or an HTML…
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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 Exfiltration
net-credential-useSKILL.md:56Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host; quoted — discussed, not commanded)echo "$MY_KEY" | byagent login --api https://app.byagent.dev
vendor-hostquoted
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 530 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 48/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. 30 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 60Consistency. The Hermes dialect needs category and tags
- 100Steps. 5 steps
- 100Execution cost. Instruction body is 2573 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- high The skill tells the model to perform an irreversible action with no human approval
- low The response is described with custom markup (6 tags): a typed call is more reliable
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 530: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (3 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.