BF free-ai-token
Global AI money-saver: find FREE or cheap LLM API tokens/keys, free AI apps (no key), and low-cost AI memberships (region deals for Claude/OpenAI/Gemini; Turkey/India/Argentina subscriptions); auto-registers accounts and wires keys into agents (Cherry Studio/Chatbox/NextChat/LobeChat/Dify); scheduled scans via /deals /scan. 免费token · 白嫖AI · 低价API · 便宜AI会员 · 怎么免费用AI · 免费AI产品 · cheapest API · free API key · AI membership deal · cheap AI subscription. NOT for general AI pricing questions or ordinary chat/translation.
Global AI money-saver: find FREE or cheap LLM API tokens/keys, free AI apps (no key), and low-cost AI memberships (region deals for Claude/OpenAI/Gemini…
As a process F 50/100 · Will not run — References files that are not bundled: references/i18n/<lang>.json, references/agents/*, references/agents/*.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 · 0
✓ No critical or high findings
Files scanned: 26. 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: references/i18n/<lang>.json - warning
missing-refreference to a missing file: references/agents/* - warning
missing-refreference to a missing file: references/agents/*.md
Process rating: all ten parameters 50/100
- 0Tools and files. 3 referenced file(s) missing: references/i18n/<lang>.json, references/agents/*, references/agents/*.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 6 mutating operations with no state check
- 70Execution cost. Instruction body is 4155 tokens
- 100Steps. 31 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 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
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 519: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 31 items
- +4Reference files are cited in the instructions (11 of 11)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.