CtrlK
BlogDocsLog inGet started
Tessl Logo

ts-sdk-account

How to create and use Account (signer) in @aptos-labs/ts-sdk. Covers Account.generate(), fromPrivateKey(), fromDerivationPath(), Ed25519 vs SingleKey vs MultiKey vs Keyless, serialization (fromHex/toHex). Triggers on: 'Account.generate', 'Account.fromPrivateKey', 'Ed25519PrivateKey', 'SDK account', 'mnemonic', 'SingleKeyAccount', 'KeylessAccount'.

68

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable reference with executable code throughout and clear guardrails. The main gap is the absence of an explicit workflow with validation checkpoints for the sensitive signing/transaction operations.

Suggestions

Add a short end-to-end workflow (generate/load key -> build transaction -> sign -> verify signature -> submit) with an explicit 'verify before submit' validation checkpoint to lift workflow_clarity.

De-duplicate the 'Common mistakes' table against the ALWAYS/NEVER lists, or fold one into the other, to reduce redundancy and save tokens.

Consider moving the four typed AccountUtils.fromHex deserializers into a references file to slim the inline API surface and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and code-dense with minimal prose padding, but the 'Common mistakes' table partially restates the ALWAYS/NEVER guardrails, a minor redundancy that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready, executable TypeScript for every common case — generate, fromPrivateKey, fromDerivationPath, serialization, signing, and verification — with correct imports and realistic arguments.

5 / 5

Workflow Clarity

Individual operations are clear and the ALWAYS/NEVER lists provide guardrails, but there is no explicit multi-step sequence or validation checkpoint for sensitive signing/transaction operations, and the 'Verify signature' step is not framed as a workflow checkpoint.

3 / 5

Progressive Disclosure

Content is organized into clear, well-labeled sections with one-level-deep external references (related skills, SDK source files), though the full API reference is inlined since no bundle files exist to defer detail to.

4 / 5

Total

16

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states both what the skill does and when to use it, with concrete API-level triggers. Only minor improvement possible by adding a few more natural-language synonyms to the trigger list.

DimensionReasoningScore

Specificity

Lists multiple concrete API actions — Account.generate(), fromPrivateKey(), fromDerivationPath(), Ed25519 vs SingleKey vs MultiKey vs Keyless, and serialization (fromHex/toHex) — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers 'what' (create and use Account, covering the listed APIs and schemes) and 'when' via a concrete 'Triggers on:' clause with specific trigger phrases.

5 / 5

Trigger Term Quality

Provides seven natural trigger terms users would actually say ('Account.generate', 'SDK account', 'mnemonic', 'SingleKeyAccount', 'KeylessAccount'), but omits a few common synonyms like 'private key', 'signer', or 'derivation path'.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (@aptos-labs/ts-sdk Account/signer) with class-name-specific triggers, making conflict with unrelated skills unlikely.

5 / 5

Total

19

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 4 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository
aave/aptos-aave-v3
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.