BF ts-sdk-client
How to create and configure the Aptos client (Aptos, AptosConfig) in @aptos-labs/ts-sdk. Covers Network, fullnode/indexer/faucet URLs, singleton pattern, and Bun compatibility. Triggers on: 'Aptos client', 'AptosConfig', 'SDK client', 'client setup', 'new Aptos(', 'Network.TESTNET', 'Network.MAINNET'.
As a process F 39/100 · Will not run — References files that are not bundled: ../../../../patterns/fullstack/TYPESCRIPT_SDK.md, ../ts-sdk-account/SKILL.md, ../ts-sdk-transactions/SKILL.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: 2. 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: ../../../../patterns/fullstack/TYPESCRIPT_SDK.md - warning
missing-refreference to a missing file: ../ts-sdk-account/SKILL.md - warning
missing-refreference to a missing file: ../ts-sdk-transactions/SKILL.md - warning
missing-refreference to a missing file: ../ts-sdk-wallet-adapter/SKILL.md - warning
missing-refreference to a missing file: ../use-ts-sdk/SKILL.md
Process rating: all ten parameters 39/100
- 0Tools and files. 5 referenced file(s) missing: ../../../../patterns/fullstack/TYPESCRIPT_SDK.md, ../ts-sdk-account/SKILL.md, ../ts-sdk-transactions/SKILL.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
- 30Running it twice. 2 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Steps. 15 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1148 tokens
- 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 302: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (5 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.