CtrlK
BlogDocsLog inGet started
Tessl Logo

meta-content-publish-pipeline

Use this meta-skill instead of answering directly when the user wants to turn an idea, research, notes, talk, or document into publishable blog, social, Xiaohongshu, Zhihu, slide, newsletter, or short-video content through multi-skill orchestration.

50

Quality

56%

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 ./src/opensquilla/skills/exp/meta-content-publish-pipeline/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

30%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 markdown body is essentially empty — a title and one restating sentence — while the entire multi-step publishing workflow is encoded in the YAML composition frontmatter. This makes the body non-actionable and workflow-opaque, even though it is token-efficient.

Suggestions

Add a concise "## Pipeline" section to the body that enumerates the composition steps (intake → clarify → research → source_digest → channel_strategy → publish_pack) so the workflow is visible without parsing YAML.

Include a validation/checklist checkpoint in the body for the publishing pack step (e.g., what needs human approval) to satisfy the batch-operation feedback-loop requirement.

Document each referenced sub-skill (multi-search-engine, summarize) inline or via a references/ file so the orchestration surface is discoverable.

DimensionReasoningScore

Conciseness

The two-line body is lean with no padding or over-explanation of concepts Claude already knows, though the single sentence "Transforms one idea or source packet into multi-channel publishing drafts" largely restates the frontmatter description, a minor redundancy.

4 / 5

Actionability

The body only describes ("Transforms one idea or source packet into multi-channel publishing drafts") with no concrete code, commands, or steps — it instructs nothing executable.

1 / 5

Workflow Clarity

The body contains no sequence of steps and no validation checkpoints; the actual pipeline (intake → clarify → research → digest → strategy → publish_pack) lives entirely in the YAML composition frontmatter, which is outside the evaluated body scope.

1 / 5

Progressive Disclosure

A single H1 title gives minimal structure and no bundle files exist to navigate to, but the body does not serve as an overview that signals where the real pipeline detail lives, leaving organization weak.

3 / 5

Total

9

/

20

Passed

Description

83%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 well-constructed: it explicitly states the trigger condition ("Use this meta-skill ... when the user wants to"), lists concrete input and output types, and carves out a distinct multi-channel publishing niche. It is comprehensive on channels while staying concise.

DimensionReasoningScore

Specificity

Enumerates concrete input types ("idea, research, notes, talk, or document") and output channels ("blog, social, Xiaohongshu, Zhihu, slide, newsletter, or short-video content") with the action "turn ... into publishable ... content through multi-skill orchestration" — several specific concrete items with minor gaps in action variety.

4 / 5

Completeness

Explicitly answers both what ("turn ... into publishable ... content through multi-skill orchestration") and when ("Use this meta-skill instead of answering directly when the user wants to turn an idea ...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user-facing terms like "blog", "newsletter", "Xiaohongshu", "Zhihu", "short-video", and "social" give good keyword coverage, though a few common synonyms (e.g., "post", "article") are missing.

4 / 5

Distinctiveness Conflict Risk

The meta-skill framing ("instead of answering directly") and the specific multi-channel publishing niche make it mostly distinct, with only minor overlap risk against single-channel writing skills.

4 / 5

Total

17

/

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.

Validation13 / 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
TokenRhythm/opensquilla
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.