content

Use Content for repo-backed Markdown/MDX docs, blogs, resources, rich document editing, local components, shareable copies, and Content local-file workspaces. Prefer Content actions over raw filesystem writes when available.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/content/SKILL.md

Quality

Content

87%

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

A concise, highly actionable, well-organized body with executable commands and a justified inline manifest; the main gap is the absence of explicit validation/verification checkpoints around destructive operations.

Suggestions

Add an explicit verify step after destructive/batch operations (e.g. 'After delete-document or update-document, run get-document to confirm the change before refreshing the UI') to add a feedback loop.

Call out a brief pre-flight check before delete-document (confirm the id resolves, warn the user) so the destructive path has a checkpoint.

Consider splitting the full agent-native.json manifest block into a reference file if future sections grow, keeping SKILL.md as a tighter overview.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it avoids explaining what Markdown/MDX or frontmatter are, and each section (decision logic, action examples, manifest, boundaries) earns its place without padding.	3 / 3
Actionability	It provides copy-paste-ready, executable commands (`pnpm action list-documents`, `npx @agent-native/core@latest skills add content ...`) plus concrete JSON action-call examples and a real manifest, fully meeting the executable-guidance anchor.	3 / 3
Workflow Clarity	A sequence is present ('pull-document/get-document before editing', 'edit-document vs update-document', 'refresh-list after create/update/delete') but there are no explicit validation/verification checkpoints for destructive operations like delete-document, which caps workflow clarity at 2 per the guidelines.	2 / 3
Progressive Disclosure	The skill is self-contained with no nested or multi-level references and is organized into clearly labeled sections (Choose The Path, Action Examples, Local File Mode, MDX And Components, Boundaries); there is no content that clearly must be split out, so the well-organized-sections bar is met.	3 / 3
	Total	11 / 12 Passed

Description

72%

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 solid, domain-rich description with good natural trigger terms and a distinct niche, but it lacks an explicit 'Use when...' trigger clause and leans on domain nouns rather than concrete verbs.

Suggestions

Add an explicit trigger clause such as 'Use when the user asks to author, edit, review, or publish Markdown/MDX docs, blogs, or resource pages' to raise completeness to 3.

Reframe some domain nouns as concrete actions (e.g. 'create, edit, and publish Markdown/MDX docs and blogs; build local MDX components') to strengthen specificity.

Drop or soften jargon like 'Content local-file workspaces' and 'repo-backed' in favor of plainer phrasing users would actually say.

Dimension	Reasoning	Score
Specificity	The description lists concrete domains ('repo-backed Markdown/MDX docs, blogs, resources, ... local components, shareable copies') and a couple of actions ('rich document editing', 'shareable copies'), but the framing 'Use Content for [nouns]' names domains more than concrete verbs, so it stops short of the 'lists multiple specific concrete actions' anchor.	2 / 3
Completeness	It clearly answers 'what' (Content for repo-backed MDX docs/blogs/resources/components) but the 'when' is only implied via 'Use Content for...'; there is no explicit 'Use when...' trigger clause, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Natural user-facing terms are well covered — 'docs', 'blogs', 'resources', 'Markdown/MDX', 'document editing' — matching the 'good coverage of natural terms users would say' anchor.	3 / 3
Distinctiveness Conflict Risk	The Content-app-specific framing with MDX, local components, local-file workspaces, and shareable copies carves a clear niche that is unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: BuilderIO/agent-native
Path: skills/content/SKILL.md
Commit: e9a2f0e

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.