repurpose-content

Turn one source piece (blog, newsletter, transcript) into platform-native posts for X and LinkedIn.

Quality

66%

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 ./runtime/api-server/src/embedded-capabilities/content-repurposer/skills/repurpose-content/SKILL.md

Quality

Content

80%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 body is a lean, well-organized, actionable 5-step workflow with no token waste and good structure. Its main weakness is the absence of any validation/verification checkpoint for the batch output of multiple platform posts, which caps workflow clarity at 3.

Suggestions

Add a verification checkpoint before returning drafts, e.g. confirm X posts fit character limits and each LinkedIn post has a concrete takeaway.

Consider one short inline example (a before/after hook) to push actionability toward fully executable anchor 5.

Optionally note an explicit review/publish handoff step with the twitter_* / linkedin_* tools so the validation loop is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is ~10 lean lines with no over-explanation of concepts Claude already knows (no definition of a blog or a thread); every line gives a concrete instruction. Fits anchor 5 ('lean and efficient; assumes Claude's competence; every token earns its place').	5 / 5
Actionability	Gives concrete, specific guidance ('pull the 3-5 ideas', 'a thread for the strongest idea', 'concrete opening line, a short story or insight, then a takeaway', 'No hashtag spam', 'match the tone of their recent posts'). As an instruction-only skill code absence is not penalized, but it stops short of copy-paste-ready examples/templates, so anchor 4 rather than 5.	4 / 5
Workflow Clarity	A clear 5-step sequence is present, but the skill produces a batch of posts with no validation/verification checkpoint (no character-limit checks for X, no review-before-publish loop), and the judging guidelines cap workflow_clarity at 3 for batch operations missing validation. Not 2 because the sequence is well defined; capped at 3 rather than 4 by the batch-validation rule.	3 / 5
Progressive Disclosure	The skill is under 50 lines, needs no external references, and is organized as a clean titled intro plus numbered steps. Per the simple-skill guideline, this fits anchor 5 ('clear overview with well-organized sections') for short single-purpose skills.	5 / 5
	Total	17 / 20 Passed

Description

53%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 concrete and clearly states what the skill does with named source types and target platforms, but it lacks an explicit 'Use when...' trigger clause and natural synonyms (e.g., Twitter, social media), capping completeness and trigger-term quality at 3. It is a distinct, reasonably specific skill that would benefit from explicit when-to-use guidance.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when repurposing a blog, newsletter, or transcript into posts for X/Twitter or LinkedIn.'

Include synonyms users naturally say — 'Twitter', 'social media', 'repurpose', 'thread' — to improve trigger-term coverage.

Optionally mention a second concrete action (e.g., 'pulls the strongest ideas and drafts a thread') to lift specificity toward anchor 4.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action (turn a source into platform-native posts) elaborated with source types and two target platforms, but does not list several distinct actions. Fits anchor 3 ('1-2 concrete actions, not comprehensive') rather than 4, which requires multiple distinct actions.	3 / 5
Completeness	The 'what' is clear ('Turn one source piece ... into platform-native posts for X and LinkedIn'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. Not 2 because the 'what' is concrete; not 4 because 'when' is only weakly implied, not stated.	3 / 5
Trigger Term Quality	Includes relevant natural terms ('blog', 'newsletter', 'transcript', 'X', 'LinkedIn', 'posts') but misses common synonyms users would say such as 'Twitter', 'social media', or 'repurpose'. Fits anchor 3 ('some relevant keywords but missing common variations or synonyms') rather than 4, which needs fuller coverage.	3 / 5
Distinctiveness Conflict Risk	Targets a distinct niche (cross-platform content repurposing for X and LinkedIn) with specific source types, so conflict risk is minor. Fits anchor 4 ('mostly distinct; minor overlap risk with closely related skills') rather than 5 because the missing explicit trigger guidance leaves slight overlap with generic writing/posting skills.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: holaboss-ai/holaOS
Path: runtime/api-server/src/embedded-capabilities/content-repurposer/skills/repurpose-content/SKILL.md
Commit: 4684714

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.