BF use-ts-sdk
Orchestrates TypeScript SDK integration for Aptos dApps. Routes to granular skills for specific tasks (client setup, accounts, transactions, view functions, types, wallet adapter). Use this skill for fullstack dApp integration or when multiple SDK concerns are involved. Triggers on: 'typescript sdk', 'ts-sdk', 'aptos sdk', 'SDK setup', 'interact with contract', 'call aptos', 'aptos javascript', 'frontend integration', 'fullstack'.
As a process F 48/100 · Will not run — References files that are not bundled: ../ts-sdk-client/SKILL.md, ../ts-sdk-account/SKILL.md, ../ts-sdk-address/SKILL.md
How to improve
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../ts-sdk-client/SKILL.md - warning
missing-refreference to a missing file: ../ts-sdk-account/SKILL.md - warning
missing-refreference to a missing file: ../ts-sdk-address/SKILL.md - warning
missing-refreference to a missing file: ../ts-sdk-transactions/SKILL.md - warning
missing-refreference to a missing file: ../ts-sdk-view-and-query/SKILL.md - warning
missing-refreference to a missing file: ../ts-sdk-types/SKILL.md - warning
missing-refreference to a missing file: ../ts-sdk-wallet-adapter/SKILL.md - warning
missing-refreference to a missing file: ../../../../patterns/fullstack/TYPESCRIPT_SDK.md
Process rating: all ten parameters 48/100
- 0Tools and files. 8 referenced file(s) missing: ../ts-sdk-client/SKILL.md, ../ts-sdk-account/SKILL.md, ../ts-sdk-address/SKILL.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
- 50Failures and branches. 0 branches, has a failure section
- 85Steps. 35 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2371 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
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 434: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 35 items
- +4Has examples (5 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.