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

65%

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

68%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 skill body is well-structured, concise, and actionable with concrete commands and a real install path, but destructive operations lack validation checkpoints and the inline manifest could optionally live in a reference file. Adding a verify step after deletes/updates would lift the workflow score.

Suggestions

Add an explicit validation/verification checkpoint after destructive or batch operations (e.g. re-fetch with `get-document` after `delete-document`/`update-document` to confirm the result) to satisfy the workflow-clarity anchor above 3.

Provide at least one fully-resolved `edit-document`/`update-document` example with a real `local-file:` id value instead of a `...` placeholder to make examples copy-paste ready.

Consider moving the full `agent-native.json` manifest example into a reference file and summarizing it inline, which would tighten the body and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence without explaining basic concepts, though a few prose sentences (e.g. the local-file-model caveats) could be trimmed slightly.	4 / 5
Actionability	Provides concrete executable commands with JSON payloads (list/get/edit/update/share-document) plus a real install command and manifest, but examples rely on `local-file:...` placeholders rather than fully copy-paste-ready invocations.	4 / 5
Workflow Clarity	There is a clear edit sequence (pull/get before edit, refresh-list after create/update/delete), but destructive operations like `delete-document` lack explicit validation or verification checkpoints, capping the score at 3.	3 / 5
Progressive Disclosure	Well-organized into clear sections with no nested or external references (no bundle files present); the inline manifest JSON is somewhat bulky but contextual, keeping it just short of a 5.	4 / 5
	Total	15 / 20 Passed

Description

61%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 covers a broad, concrete set of Content use cases with natural trigger terms and a distinct niche, but it omits an explicit "Use when..." trigger clause, capping completeness. Rewording to lead with a capability statement and add explicit triggers would raise it.

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 satisfy the completeness anchor.

Lead with a third-person capability statement (e.g. "Authors, edits, and publishes repo-backed Markdown/MDX documents") before the use-case list to sharpen specificity.

Include natural synonyms and file extensions (e.g. ".md", ".mdx", posts, articles, publishing) to push trigger-term coverage toward comprehensive.

Dimension	Reasoning	Score
Specificity	Enumerates concrete content domains ("repo-backed Markdown/MDX docs, blogs, resources, rich document editing, local components, shareable copies") but the actual action verbs are limited to editing and sharing, leaning on domain nouns rather than crisp actions.	3 / 5
Completeness	Clearly states what Content is for, but lacks an explicit "Use when..." trigger clause with concrete trigger phrases, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural user terms like "docs", "blogs", "resources", "Markdown/MDX", and "editing", giving good keyword coverage with only minor synonyms missing (e.g. posts/articles, publishing).	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche around repo-backed MDX docs/blogs with local components tied to the specific Content app, with only minor overlap risk against generic markdown-editing skills.	4 / 5
	Total	14 / 20 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: bb282b1

Reviewed: ~21 hours 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.