CtrlK
BlogDocsLog inGet started
Tessl Logo

build-content-websites

构建以内容实体的发布、发现、阅读、引用、修订与归档为核心的网站;适用于单篇出版物、小型静态站、出版或机构站、文档与知识库、目录与档案、CMS 内容产品及内容迁移;不用于渠道图形、组件系统本体,或以反复操作业务对象为核心的产品界面。

59

Quality

68%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins-dist/design-engine/raven_design/skills/build-content-websites/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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 workflow is rigorously sequenced with strong validation gates and feedback loops, but the dense governance prose trades conciseness for readability and the actionability is mostly contractual rather than executable. A dangling reference to references/benchmarks/ and the monolithic structure limit progressive disclosure.

Suggestions

Resolve or remove the dangling reference to references/benchmarks/ in §3 (内容机制标杆) — either create the directory or point at an existing file.

Move the bulky gate tables, claim-family definitions, and authority-graph mappings into a reference file so SKILL.md stays a lean overview with one-level-deep links.

Add a few concrete executable snippets (e.g., a sample capability-probe command, a build/verify invocation) to lift actionability beyond contractual instructions.

DimensionReasoningScore

Conciseness

It assumes Claude's competence (no basic concept padding) and is dense, but the jargon-heavy governance prose and repetition across sections (gate tables, pitfalls, checklist restate the same rules) could be tightened into fewer tokens.

3 / 5

Actionability

It names concrete artifacts and enums (identity_route, visual_role, D11_* gates, SURFACE-MANIFEST, claim families), but as an instruction-only skill it provides almost no executable code or commands, leaving the actual build mechanics implicit.

3 / 5

Workflow Clarity

Clear numbered sequence (sections 1–6) with explicit D11_* gate table columns including 失败返回, a 域内险境 pitfall-to-gate feedback loop, and a final checklist — validation checkpoints and error-recovery loops are explicit throughout.

5 / 5

Progressive Disclosure

The body signals one-level-deep references (references/patterns.md, references/tool-profiles.md) and those files exist, but references/benchmarks/ is cited in §3 and does not exist, and the body itself is a large monolithic governance wall that could be split out.

3 / 5

Total

14

/

20

Passed

Description

75%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 specific, distinguishes its niche with explicit in/out boundaries, and covers both what and when in third person. It would score higher with more natural 'Use when...' trigger phrasing and synonym/extension coverage.

Suggestions

Reframe the trigger as an explicit 'Use when... / 不用于...' clause with the natural phrases a user would actually say (e.g., '文档站、知识库、出版站、CMS 迁移').

Add common synonyms and concrete signals (e.g., .md content corpus, sitemap, RSS/feed) to broaden trigger-term coverage.

Tighten the abstract '内容实体' framing toward user-recognizable objects so the trigger does not lean on jargon.

DimensionReasoningScore

Specificity

Names the domain (content-entity websites) and enumerates concrete subtypes — 单篇出版物、小型静态站、出版/机构站、文档/知识库、目录/档案、CMS 内容产品及内容迁移 — plus explicit exclusion cases; minor coverage gaps keep it just below comprehensive.

4 / 5

Completeness

Clearly states what it builds (发布、发现、阅读、引用、修订与归档为核心的网站) and gives an explicit 适用于... 'when' clause with exclusions (不用于...), but the trigger phrasing is not framed as a natural 'Use when...' clause, so it is not maximally explicit.

4 / 5

Trigger Term Quality

Includes natural terms users would say (出版物、文档、知识库、目录、档案、CMS、内容迁移) but leans on the abstract phrase 内容实体 and omits file-extension/synonym variants, so a few natural terms are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (content-entity publishing sites) with explicit boundary exclusions against 渠道图形, 组件系统本体, and 业务对象产品界面; minor overlap risk with general site-building skills.

4 / 5

Total

16

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
EverMind-AI/Raven
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.