CtrlK
BlogDocsLog inGet started
Tessl Logo

create-linkedin-content

Draft voice-tuned LinkedIn post variants from a free-form brief. Reads a personal voice guide (generated via generate-voice-guide), produces 2–5 variants with distinct framings, applies LinkedIn-specific defaults (arrow bullets, "why this matters" beat, 150–500 words), and self-checks against the voice guide's banned phrases before returning.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured, concise, and highly actionable, with a clear six-phase workflow anchored by an explicit self-check validation phase. It appropriately keeps everything inline for a cohesive instruction skill without over-explaining basics.

DimensionReasoningScore

Conciseness

The body is lean and task-specific, deliberately mirroring create-x-content to avoid restating shared logic, and does not explain concepts Claude already knows (e.g., what LinkedIn is).

3 / 3

Actionability

Although instruction-only, the guidance is concrete and copy-ready: a framings table with structures and use-cases, specific defaults (arrow bullets, 150–500 words), a frontmatter template, a file-naming convention, and worked examples.

3 / 3

Workflow Clarity

The six phases are clearly sequenced, and Phase 4 is an explicit self-check validation gate with seven concrete checks and remediation guidance ('If yes, rewrite to sound like a human practitioner') before outputs are saved.

3 / 3

Progressive Disclosure

It is a single self-contained file with well-organized sections and clear headings, and references to sibling skills are one level deep and clearly signaled; no nested or monolithic references to penalize.

3 / 3

Total

12

/

12

Passed

Description

67%

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, third-person, and well-differentiated, clearly conveying what the skill does. Its main gap is the absence of an explicit 'Use when…' trigger clause, which leaves the invocation context implied rather than stated.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to draft LinkedIn posts or asks for LinkedIn content in their own voice.'

Broaden trigger terms to include common user phrasings like 'LinkedIn posts', 'LinkedIn updates', or 'write a LinkedIn post in my voice'.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('Draft voice-tuned LinkedIn post variants', 'produces 2–5 variants with distinct framings', 'applies LinkedIn-specific defaults', 'self-checks against the voice guide's banned phrases'), matching the highest anchor.

3 / 3

Completeness

It clearly answers 'what' the skill does, but lacks an explicit 'Use when…' trigger clause telling Claude when to invoke it; per the judging guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

It includes relevant natural terms ('LinkedIn post variants', 'free-form brief', 'voice guide') but does not cover common variations users might say (e.g., 'LinkedIn posts', 'social posts', 'write a LinkedIn update'), so coverage is good but not comprehensive.

2 / 3

Distinctiveness Conflict Risk

The LinkedIn-specific framing plus the voice-guide dependency carve out a clear niche with distinct triggers, making it unlikely to fire for the wrong sibling skill.

3 / 3

Total

10

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
gooseworks-ai/goose-skills
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.