CtrlK
BlogDocsLog inGet started
Tessl Logo

self-modifying-code

Tiers, checkpoints, and off-limits paths for an agent editing the app's own source. Use when designing UI for agent editability, deciding whether a file is safe for the agent to change, or when tempted to patch config, `.env`, or an `@agent-native/*` package. Do not load it for ordinary source edits.

70

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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-structured, highly actionable policy skill: concrete commands, executable snippets, and a validated checkpoint workflow for source modification. Its only weaknesses are minor redundancy between the taxonomy and the 'Don't' list, and a single-file structure that could offload some detail to reference files now that it has grown past a simple skill.

DimensionReasoningScore

Conciseness

The body is dense policy content — a tier table, specific commands, and short code snippets — with no padding explaining concepts Claude already knows. Minor trimming is possible: the 'Don't' list repeats the Tier 4 prohibitions already enumerated in the Modification Taxonomy section, and the eject paragraph ('Manual copying is only the fallback described by an unknown third-party package's add-style blueprint') is convoluted. This fits the 4 anchor (efficient with minor instances that could be trimmed) rather than the 3 anchor's 'some unnecessary explanation', since nothing is concept padding.

4 / 5

Actionability

Guidance is fully executable: copy-paste commands ('pnpm typecheck && pnpm lint', 'git checkout -- <file>', 'npx @agent-native/core@latest upgrade', 'agent-native upgrade', 'agent-native eject'), concrete TypeScript snippets for `data-*` attributes and `window.__appState`, and a tier table with specific file examples. Specific examples cover the common cases, matching the 5 anchor.

5 / 5

Workflow Clarity

The Git Checkpoint Pattern is a numbered 5-step sequence with an explicit validation step ('Run `pnpm typecheck && pnpm lint`') and a feedback loop on failure ('If verification fails → revert with `git checkout -- <file>`'), and the tier table adds per-tier validation requirements ('Ask for explicit approval first', 'Never modify these'). This matches the 5 anchor — clear sequence, explicit validation, error-recovery loop — including for the destructive operation of source modification.

5 / 5

Progressive Disclosure

There are no bundle files (no references/, scripts/, or assets/ directories), so all content lives in the well-sectioned SKILL.md body (~124 lines). Sections are clearly organized (Rule, Why, Taxonomy, Checkpoint, Designing, Don't, Related Skills) and cross-skill pointers are clearly signaled one level deep ('upgrade-agent-native', 'customizing-agent-native', 'internationalization'). This fits the 4 anchor (good structure, references mostly clear, minor organization gaps) rather than 5, since the body exceeds the under-50-line simple-skill case and some detail (e.g., the eject/upgrade rules or the design patterns) could be offloaded to reference files.

4 / 5

Total

18

/

20

Passed

Description

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

A strong description: it clearly states what the skill covers and when to use it, with concrete file and package triggers and an explicit negative trigger that sharply bounds scope. Keyword coverage is good but could include a few more natural synonyms users might phrase differently.

DimensionReasoningScore

Specificity

The description names the domain ('Tiers, checkpoints, and off-limits paths for an agent editing the app's own source') and several concrete actions ('designing UI for agent editability, deciding whether a file is safe for the agent to change', 'tempted to patch config, `.env`, or an `@agent-native/*` package'). It lists several specific actions but they are topic categories rather than the fully enumerated, comprehensive action list of the 5 anchor, so it sits above the 1-2 concrete actions of the 3 anchor.

4 / 5

Completeness

It explicitly answers both questions: what ('Tiers, checkpoints, and off-limits paths for an agent editing the app's own source') and when ('Use when designing UI for agent editability, deciding whether a file is safe... or when tempted to patch config, `.env`, or an `@agent-native/*` package'), with a concrete negative scope guard ('Do not load it for ordinary source edits') that sharpens the 'when'. This matches the 5 anchor's explicit what + when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases are present and domain-specific — 'designing UI for agent editability', 'deciding whether a file is safe for the agent to change', 'patch config, `.env`, or an `@agent-native/*` package', plus the negative trigger 'Do not load it for ordinary source edits'. Coverage is good with concrete file/package names, but it misses some common variations users might say (e.g., 'self-modifying', 'editing its own code'), so it falls just short of the comprehensive synonym coverage of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (rules for an agent editing its own app's source) with distinct, specific triggers, and the explicit exclusion ('Do not load it for ordinary source edits') prevents it from firing on routine edits — minimal conflict risk with generic coding skills, matching the 5 anchor.

5 / 5

Total

18

/

20

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 — 13 / 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

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
BuilderIO/agent-native
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.