BF token-management
Centralized API token management workflow. Store tokens in .env with expiration dates, test permissions via script battery, document capabilities in connections/, set calendar renewal reminders. Prevents re-asking for credentials, ensures token security, tracks expiration.
Centralized API token management workflow.
As a process F 33/100 · Will not run — References files that are not bundled: ~/Documents/life/connections/figma.md, ~/Documents/life/connections/jira.md, ~/Documents/life/connections/slack.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
read-dotenvSKILL.md:152Reads a .env file (documentation of a security skill)cat ~/Documents/life/.env
security skill -
low Exfiltration
read-dotenvSKILL.md:175Reads a .env file (documentation of a security skill)source ~/Documents/life/.env
security skill
Files scanned: 1. 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") - warning
missing-refreference to a missing file: ~/Documents/life/connections/figma.md - warning
missing-refreference to a missing file: ~/Documents/life/connections/jira.md - warning
missing-refreference to a missing file: ~/Documents/life/connections/slack.md - warning
missing-refreference to a missing file: ~/Documents/life/connections/github.md - note
frontmatter-keyunknown frontmatter key "type" - note
frontmatter-keyunknown frontmatter key "status" - note
frontmatter-keyunknown frontmatter key "dependencies"
Process rating: all ten parameters 33/100
- 0Tools and files. 4 referenced file(s) missing: ~/Documents/life/connections/figma.md, ~/Documents/life/connections/jira.md, ~/Documents/life/connections/slack.md
- 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. 6 mutating operations with no state check
- 100Steps. 37 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1224 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
- +2Single-language instructions
- +3Description length 273: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 37 items
- +4Has examples (8 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.