CtrlK
BlogDocsLog inGet started
Tessl Logo

ast-grep

Use ast-grep (sg) for AST-aware code search and rewrite across 25 languages. Trigger for structural code matching or deterministic codemods: find every function/call/class/import shaped like X, rewrite console.log to logger.info, strip `as any`, migrate require() to import, find empty catch blocks or missing await, and scan/apply YAML rules. Prefer this over rg/grep when the target is syntax shape rather than text; use rg for string contents, comments, filenames, or regex-style byte searches.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 is dense, executable, and well-structured: concrete commands throughout, an explicit dry-run-first workflow with validation checkpoints, and clean one-level-deep references to a complete bundle. It avoids teaching concepts Claude already knows.

DimensionReasoningScore

Conciseness

Lean and token-efficient: no padding explaining what ASTs or libraries are, dense tables, and a decision tree that earns every token; assumes Claude's competence throughout.

5 / 5

Actionability

Copy-paste-ready commands for every helper subcommand and direct `sg` idiom, covering search, replace (dry-run and apply), scan, validate, and debug flows with concrete flags.

5 / 5

Workflow Clarity

Multi-step rewrite workflow is explicitly sequenced (search → dry-run → inspect → refine-or-apply) with a feedback loop, plus a prioritized 0-matches debugging triage and validation invariants for destructive/batch operations.

5 / 5

Progressive Disclosure

Clear overview in SKILL.md pointing one level deep to 7 real reference files and a helper script, with a prioritized 'Required reading' list and explicit per-file triggers; all referenced paths exist.

5 / 5

Total

20

/

20

Passed

Description

100%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 precise, action-oriented, and rich with concrete trigger phrases and a clear when-to-use boundary. It comprehensively covers capabilities while remaining scannable and distinct from rg/grep-based search skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (find every function/call/class/import, rewrite console.log to logger.info, strip `as any`, migrate require() to import, find empty catch blocks or missing await, scan/apply YAML rules), giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (AST-aware search and rewrite across 25 languages, scan/apply YAML rules) and 'when' ('Trigger for structural code matching...', 'Prefer this over rg/grep when the target is syntax shape rather than text').

5 / 5

Trigger Term Quality

Rich natural-language triggers users actually say ('find every', 'rewrite', 'codemod', 'empty catch blocks', 'missing await') plus synonyms (ast-grep/sg) and explicit rg/grep boundary terms.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (structural/AST matching) and draws an explicit boundary against rg/grep for text-shaped queries, minimizing wrong-skill conflict.

5 / 5

Total

20

/

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
code-yeongyu/lazycodex
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.