CtrlK
BlogDocsLog inGet started
Tessl Logo

code-import

Read an existing repository's structure into the project cwd as a normalised snapshot the agent can analyse without re-walking the tree on every turn.

44

Quality

46%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/_official/atoms/code-import/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured and lean, with a clear input/output model and useful anti-patterns, but it describes rather than instructs: there is no executable code, no explicit validation feedback loop for the batch walk, and the actual mechanics are deferred to an external implementation file.

Suggestions

Add an explicit validation checkpoint with a fix-and-retry loop for the batch tree walk (e.g. verify index.json has entries, re-walk on failure) so workflow_clarity can reach 3.

Provide executable or near-executable guidance for producing the snapshot rather than only describing the output schema and deferring to the daemon implementation file.

Trim the rationale prose and internal Spec citations to tighten conciseness toward the top anchor.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes competence without explaining basic concepts, but prose like "The point is to stop re-walking the tree on every turn" and the Spec §10/§21.3.2 citations add padding that could be tightened.

2 / 3

Actionability

It gives concrete input and output schemas but no executable code or commands; the "Status" section points to an implementation file rather than instructing how to perform the walk, leaving key operational details missing.

2 / 3

Workflow Clarity

The sequence (walk -> write index.json -> convergence) is present and empty repos raise an error event, but the batch tree-walk lacks an explicit validation checkpoint or fix-and-retry feedback loop, which caps workflow clarity at 2 for batch operations.

2 / 3

Progressive Disclosure

It is a single well-organized SKILL.md under 50 lines with clearly labeled sections and no nested references, satisfying the rubric's allowance for simple skills to score 3 on structure alone.

3 / 3

Total

9

/

12

Passed

Description

35%

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 states a concrete purpose in correct third person but is written in internal jargon rather than natural trigger terms and omits any "Use when..." guidance. It is recognizable but would not reliably surface from a user's natural-language request.

Suggestions

Reword around natural user phrasing (e.g. 'Import a repository so it can be analysed without re-scanning it every turn') and add a 'Use when...' clause naming triggers like importing a repo, starting a migration, or analyzing an existing codebase.

Drop internal jargon ('normalised snapshot', 're-walking the tree', 'project cwd') in favour of plain terms the user would actually say.

Add an explicit when-to-use sentence so completeness can reach the top anchor.

DimensionReasoningScore

Specificity

The description names a concrete action ("Read an existing repository's structure into the project cwd as a normalised snapshot") but covers a single primary action rather than the multiple specific concrete actions expected at score 3.

2 / 3

Completeness

It states what the skill does but provides no "Use when..." trigger, so the "when" guidance is missing; per the rubric a missing explicit trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

It uses technical jargon ("normalised snapshot", "re-walking the tree", "project cwd") and includes no natural keywords a user would actually say when they need this skill.

1 / 3

Distinctiveness Conflict Risk

The code-import snapshot niche is fairly distinct, but the jargon-heavy phrasing and absence of explicit triggers mean it could still overlap with other repository-handling skills.

2 / 3

Total

7

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.