CtrlK
BlogDocsLog inGet started
Tessl Logo

search-aptos-examples

Searches aptos-core and daily-move for reference implementations before writing contracts. Triggers on: 'search examples', 'find example', 'check aptos-core', 'is there an example', 'reference implementation', 'how does aptos implement', 'similar contract', 'daily-move'.

60

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/search-aptos-examples/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

The body delivers genuinely useful Aptos-specific example catalogues and executable access commands with a clear workflow and checklist. Its main weaknesses are redundancy between the category lists and discovery table, and a monolithic single-file structure with no progressive disclosure into reference files.

Suggestions

Consolidate the Step 2 category lists and the Example Discovery Table into a single source of truth to remove the duplicated example listings.

Move the per-example catalogue and the 'Common Patterns from Examples' code snippets into a references file (e.g. examples.md) and link to it from SKILL.md to improve progressive disclosure.

Trim repeated exhortations like 'Always search examples first' that appear in the Overview, ALWAYS Rules, and closing reminder, keeping the rule in one place.

DimensionReasoningScore

Conciseness

The repo-specific example catalogue earns its place, but the Step 2 category lists and the Example Discovery Table overlap heavily, and sentiments like 'Always search examples first' recur across the Overview, ALWAYS Rules, and closing line, so it could be tightened.

3 / 5

Actionability

Concrete git clone/cd/cat commands, exact source paths (e.g. 'token_objects/sources/token.move'), and a discovery table mapping tasks to key files give mostly executable guidance; the Move snippets are illustrative with elided bodies, leaving minor gaps.

4 / 5

Workflow Clarity

A clear four-step Core Workflow (Identify, Search, Review, Adapt) plus a pre-code Search Checklist sequences the process well; it lacks explicit validate-and-retry feedback loops, but none are needed for a non-destructive search skill, so it stays at 4 rather than 5.

4 / 5

Progressive Disclosure

Sections are well labeled and external repo links are clearly signaled, but with no bundle files present the entire ~370-line catalogue and pattern library is inlined in one file with redundant listings, which is content that could be split into reference files.

3 / 5

Total

14

/

20

Passed

Description

78%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.

The description clearly and explicitly answers both what the skill does and when to trigger it, with a strong set of natural trigger phrases and a well-scoped Aptos niche. It is slightly limited in specificity (one core action) and a few triggers are generic enough to risk minor overlap.

DimensionReasoningScore

Specificity

Names the domain (aptos-core, daily-move) and one concrete action ('Searches ... for reference implementations'), but does not enumerate multiple distinct actions, so it sits at the '1-2 concrete actions, not comprehensive' anchor rather than 4.

3 / 5

Completeness

Explicitly states what it does ('Searches aptos-core and daily-move for reference implementations before writing contracts') and when to use it via concrete trigger phrases, matching the 'clearly answers both what AND when' anchor.

5 / 5

Trigger Term Quality

Lists eight natural trigger phrases a user would actually say ('search examples', 'find example', 'how does aptos implement', 'similar contract'), giving strong coverage, though they are mostly variations on one concept rather than the full synonym set a 5 would require.

4 / 5

Distinctiveness Conflict Risk

The aptos-core/daily-move specificity gives it a clear niche with minimal conflict risk, but generic phrases like 'search examples' and 'find example' could overlap with broader example-search skills, keeping it just below a 5.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 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

Total

14

/

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.