ts-sdk-transactions
How to build, sign, submit, and simulate transactions in @aptos-labs/ts-sdk. Covers build.simple(), signAndSubmitTransaction(), waitForTransaction(), simulate, sponsored (fee payer), and multi-agent. Triggers on: 'build.simple', 'signAndSubmitTransaction', 'transaction.build', 'waitForTransaction', 'signAsFeePayer', 'SDK transaction', 'sponsored transaction', 'multi-agent transaction'.
78
100%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies the specific SDK, lists concrete actions and method names, and provides explicit trigger terms. It effectively communicates both what the skill does and when it should be activated, with highly distinctive terminology that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: build, sign, submit, simulate transactions, and names specific methods like build.simple(), signAndSubmitTransaction(), waitForTransaction(). Also covers sponsored (fee payer) and multi-agent transaction types. | 3 / 3 |
Completeness | Clearly answers 'what' (build, sign, submit, simulate transactions in @aptos-labs/ts-sdk with specific methods) and 'when' (explicit 'Triggers on:' clause listing specific trigger terms). Both dimensions are well-covered. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including both method names ('build.simple', 'signAndSubmitTransaction', 'waitForTransaction', 'signAsFeePayer') and conceptual terms ('SDK transaction', 'sponsored transaction', 'multi-agent transaction'). These are terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific SDK (@aptos-labs/ts-sdk), specific method names, and the Aptos blockchain domain. Very unlikely to conflict with other skills given the narrow, well-defined niche. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that covers the full transaction lifecycle in the Aptos TypeScript SDK with concise, executable examples. It respects Claude's intelligence by avoiding unnecessary explanations while providing complete, actionable code for each transaction pattern. The ALWAYS/NEVER constraints and common mistakes table add high-value guardrails without bloat.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what transactions are or how the SDK works conceptually, jumping straight into actionable patterns. The ALWAYS/NEVER lists are terse and high-value. Every section earns its place with concrete code. | 3 / 3 |
Actionability | Every section provides fully executable, copy-paste-ready TypeScript code with proper imports and realistic patterns. The standard flow, simulation, sponsored, and multi-agent examples are all complete and concrete with specific method signatures and argument structures. | 3 / 3 |
Workflow Clarity | The standard flow clearly numbers steps (build → sign/submit → wait) with explicit validation (checking `committedTx.success`). Simulation is presented as a pre-submit checkpoint. Sponsored and multi-agent flows have clear multi-step sequences with proper ordering of sign operations before submit. | 3 / 3 |
Progressive Disclosure | The skill is well-structured with a clear overview (Purpose, ALWAYS/NEVER), then progressively more advanced patterns (simple → build options → simulation → sponsored → multi-agent). References to related skills and patterns are one level deep and clearly signaled at the bottom. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 |
Total | 9 / 11 Passed | |
- Repository
- aave/aptos-aave-v3
- Commit
919362b
- 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.