CtrlK
BlogDocsLog inGet started
Tessl Logo

claude-code-usage

[AUTO-INVOKE] MUST be invoked at the START of each new coding session. Covers context management, task strategies, and Foundry-specific workflows. Trigger: beginning of any new conversation or coding session in a Solidity/Foundry project.

60

Quality

69%

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 ./data/skills-md/0xlayerghost/solidity-agent-kit/claude-code-usage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 content is a well-organized, actionable reference with strong concrete commands and clearly sequenced workflows. Its main weakness is verbosity in the Meta-Prompting section, where the extended worked example adds length without proportional value.

Suggestions

Tighten the Meta-Prompting 'Practical Example' by shortening the quoted Chinese prompts or summarizing rounds 2-4 into a compact table.

Consider splitting the Meta-Prompting templates and worked example into a reference file so SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient with well-structured tables and terse rules, but the Meta-Prompting section includes a lengthy multi-round practical example with long quoted prompts that could be tightened, fitting the mostly-efficient-with-some-unnecessary-explanation anchor.

3 / 5

Actionability

It provides concrete executable commands ('forge fmt && forge test', 'git diff', 'forge test --match-test <name> -vvvv'), specific path-based prompt examples, and a real multi-round example flow, fitting the mostly-executable guidance anchor with minor gaps.

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced (the 4-step meta-prompting flow with arrows, the Foundry before-commit/after-modify/PR workflow), and git operations include a validation checkpoint ('Always run git diff before committing'), fitting the clear-sequence-with-most-checkpoints anchor with minor gaps.

4 / 5

Progressive Disclosure

The single SKILL.md is well-organized into clearly headed sections with no nested external references, and as a self-contained skill under ~120 lines it follows the simple-skill guidance, fitting the good-structure anchor with minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

71%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 is strong on completeness, clearly stating both what the skill covers and an explicit auto-invoke trigger. It is moderately specific and distinctive, with the main weakness being category-level capability labels rather than granular concrete actions.

Suggestions

Replace category labels ('context management, task strategies') with concrete actions, e.g. 'Manages context windows, plans multi-file refactors, runs Foundry test/build workflows'.

Add natural synonyms users say, such as 'smart contract', 'Solidity contracts', or 'forge/foundry commands', to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain and a few areas ('context management, task strategies, and Foundry-specific workflows'), but these are category labels rather than multiple granular concrete actions, matching the anchor that lists 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

It explicitly answers both 'what' ('Covers context management, task strategies, and Foundry-specific workflows') and 'when' with concrete trigger phrasing ('MUST be invoked at the START of each new coding session' and 'Trigger: beginning of any new conversation or coding session in a Solidity/Foundry project'), matching the anchor for clear and explicit what AND when with concrete trigger phrases.

5 / 5

Trigger Term Quality

It includes relevant terms like 'Solidity/Foundry project' and 'new conversation or coding session', but is missing common natural synonyms a user might say such as 'smart contract' or 'Solidity contracts', fitting the anchor for some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

The Solidity/Foundry niche gives it a clear, fairly distinct trigger, though 'context management' and 'task strategies' are broad areas with minor overlap risk against general Claude Code usage skills, fitting the mostly-distinct anchor with minor overlap risk.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
NeverSight/skills_feed
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.