CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

draft-review-posts

Draft social posts and vendor feedback from a local model eval's conclusion pack, and publish only after the user approves the exact content.

Quality

82%

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

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

A lean, well-organized instruction-only skill that respects the reader's intelligence and encodes genuine domain knowledge about what makes eval posts credible. Its workflow is exemplary for an outward-facing operation — an explicit human-approval checkpoint with a re-approval loop on edits — and the only gap is the absence of a worked example post to anchor voice and format.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — "Plain sentences, no hype words, no emoji walls", "Every number in a draft must appear in report.md" — with no padding and no explanation of concepts Claude already knows; the "What makes these posts work" section contributes genuine domain insight (lead with hardware and a concrete number, honesty about limits) that earns its tokens. Not 4 because there are no instances of over-explanation to trim.

5 / 5

Actionability

Concrete, executable guidance for an instruction-only skill: four enumerated drafts with constraints ("under 280 characters plus the speed chart", save to `<run_dir>/posts/`, `vendor-feedback.md`), explicit disclosure markers (`#ad`, "Sponsored", "合作"), a named tool (`ask_user_question`), and a placeholder rule for links. Not 5 because no example post or template is provided and the speed chart's provenance is assumed from the upstream skill; not 3 because the guidance is specific and directive, far from pseudocode.

4 / 5

Workflow Clarity

Clear sequence with explicit validation checkpoints and a feedback loop: check disclosure before drafting ("If you do not know, ask the user before drafting"), show drafts, then "Show the final text and attached image, and ask for approval with ask_user_question", publish only the exact approved content, and "If the user edits it, show the new version and ask again" — proper error recovery for an outward-facing publishing operation. Not 4 because the key checkpoints are all explicit rather than mostly present.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and none are bundled; the body is well organized into clear sections ("What makes these posts work", "Drafts to produce", "Disclosure", "Publishing") with no content that should be split out. Per the simple-skill guideline, well-organized sections alone merit a 5 here.

5 / 5

Total

19

/

20

Passed

Description

62%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 specific, honest description with a clear niche and concrete actions, but it lacks any explicit when-to-use trigger guidance and omits the natural platform keywords (X, thread, share results) users would most likely say. Adding a "Use when..." clause naming the triggering context and platforms would lift completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to share or post local model eval results, write an X thread about a benchmark run, or send feedback to a model vendor."

Include natural platform keywords users would say — X/Twitter, thread, LinkedIn, Reddit, share results — so the description matches real phrasing.

Optionally enumerate the deliverable types (single post, thread, Chinese short post) to close the specificity gap toward comprehensive coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Draft social posts and vendor feedback", "publish only after the user approves the exact content" — tied to a specific source artifact ("a local model eval's conclusion pack"). Not 5 because post types and platforms are not enumerated, leaving minor coverage gaps; not 3 because it goes beyond 1-2 generic actions with a specific, grounded workflow.

4 / 5

Completeness

The "what" is clear (draft posts and vendor feedback from a conclusion pack, publish after approval), but there is no "Use when..." clause or equivalent explicit trigger guidance — the approval gating is a publishing condition, not a when-to-use trigger, so completeness is capped at 3. The phrase "from a local model eval's conclusion pack" only weakly implies the triggering context.

3 / 5

Trigger Term Quality

"social posts", "vendor feedback", and "publish" are natural terms a user might say, but the most likely trigger words — platform names (X, Twitter, thread, LinkedIn, Reddit) and phrases like "share the results" or "write a thread" — are all missing. Not 4 because the missing variations are the common ones users actually say; not 2 because the terms present are natural rather than jargon.

3 / 5

Distinctiveness Conflict Risk

A clear niche — drafting social posts and vendor feedback specifically from a local model eval's conclusion pack — with minimal conflict risk against generic posting or writing skills. Not 4 because the tie to the eval conclusion-pack artifact makes accidental triggering for a wrong skill unlikely, exceeding "minor overlap risk".

5 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

holaboss-ai/holaOS

Path

runtime/api-server/src/embedded-capabilities/local-model-review/skills/draft-review-posts/SKILL.md

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.