ts-sdk-view-and-query

How to read on-chain data in @aptos-labs/ts-sdk: view(), getBalance(), getAccountInfo(), getAccountResources(), getAccountModules(), getResource(). Triggers on: 'aptos.view', 'getBalance', 'getAccountInfo', 'getAccountResources', 'SDK query', 'view function TypeScript'.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%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 tight, code-first reference with fully executable examples across all read methods and useful ALWAYS/NEVER guardrails and lookup tables. The only real slack is minor redundancy in the deprecated-method warnings and external references that fall outside the bundle.

Suggestions

Consolidate the deprecated getAccountCoinAmount/getAccountAPTAmount guidance into a single ALWAYS-or-NEVER entry to remove the duplicated warning.

Add a one-line orientation at the top (e.g. 'Start with getBalance for APT, view() for Move reads') to give a clear entry point into the method catalog.

Verify the References paths resolve within the skill bundle, or mark them explicitly as cross-skill pointers so navigation intent is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-first with terse comments and no Aptos/Move primer, but the deprecated-method warning is stated twice (ALWAYS #1 "not deprecated getAccountCoinAmount / getAccountAPTAmount" and NEVER #1), a minor redundancy that keeps it just below the every-token-earns-its-place score-5 anchor.	4 / 5
Actionability	Each method has fully executable, copy-paste-ready code, and the view() section covers the common cases (no type args, generic coin type via typeArguments, multiple return values with destructuring), matching the score-5 anchor of fully executable examples covering common cases.	5 / 5
Workflow Clarity	As a read-only, single-purpose reference it needs no validation checkpoints, and the ALWAYS/NEVER guardrails make the single action unambiguous; it lacks an explicit "start here" sequencing entry point, so it sits at the clear-but-minor-gaps score-4 anchor rather than 5.	4 / 5
Progressive Disclosure	Content is well structured with one section per method plus type-handling and common-mistakes tables for easy navigation; no bundle files exist so there is nothing to split, but the trailing References point to paths outside the skill bundle, leaving minor organization gaps at the score-4 anchor.	4 / 5
	Total	17 / 20 Passed

Description

88%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 explicitly pairs a concrete capability list with a clear trigger clause, satisfying the what-and-when requirement. Trigger terms lean on method names over natural synonyms, and the surrounding skill family creates modest overlap risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete read actions — "view(), getBalance(), getAccountInfo(), getAccountResources(), getAccountModules(), getResource()" — giving comprehensive coverage of the SDK's read surface, matching the score-5 anchor of multiple specific concrete actions.	5 / 5
Completeness	It explicitly answers both "what" ("How to read on-chain data in @aptos-labs/ts-sdk") and "when" ("Triggers on: ..." with concrete trigger phrases), matching the score-5 anchor that requires both with concrete triggers.	5 / 5
Trigger Term Quality	The "Triggers on:" clause supplies good keyword coverage ('aptos.view', 'getBalance', 'getAccountInfo', 'getAccountResources', 'SDK query', 'view function TypeScript'), but the terms are mostly method names and miss natural synonym variations like 'aptos balance' or 'read on-chain data', so it sits below the comprehensive score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	It carves a clear read-only query niche within the Aptos TS SDK, but sibling skills referenced in the bundle (ts-sdk-client, ts-sdk-types, use-ts-sdk) create minor overlap risk with closely related skills, placing it at the mostly-distinct score-4 anchor rather than minimal-conflict score 5.	4 / 5
	Total	18 / 20 Passed

Validation

81%

Warnings & errors only

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

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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

	Total	13 / 16 Passed

Repository: aave/aptos-aave-v3
Path: .claude/skills/ts-sdk-view-and-query/SKILL.md
Commit: 919362b

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.