CtrlK
BlogDocsLog inGet started
Tessl Logo

ugc-brief

Create briefs for UGC creators including product info, hook requirements, talking points, and authenticity guidelines. Use when working with UGC creators, preparing creator packages, or scaling content production with external talent.

72

Quality

88%

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

77%

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

The body is highly actionable with a clear sequenced workflow, but it is monolithic — a long inline template plus an appended best-practices section that pads context. Splitting the template into a reference file and trimming generic UGC truisms would lift both weaker dimensions.

Suggestions

Move the ~150-line output brief template into a separate reference file (e.g. references/brief-template.md) and link to it from a concise 'Output format' section, so SKILL.md stays a lean overview.

Cut or compress the 'UGC Best Practices (LeadsIcon/Kamal)' section, which restates widely-known native-vs-polish truisms Claude already knows; keep only any non-obvious brand-specific guidance.

If keeping the template inline, add a short navigation/summary at the top so the structure is scannable without reading the whole template.

DimensionReasoningScore

Conciseness

The step structure and output template earn their place, but the appended 'UGC Best Practices (LeadsIcon/Kamal)' section restates general knowledge Claude already has ('Audiences smell BS instantly', 'Perfect = ad = skip') and could be trimmed, so it is mostly efficient but padded in places rather than lean.

2 / 3

Actionability

Provides a concrete, copy-paste-ready output template with fill-in fields, checkboxes, hook categories, and a structured talking-points flow — concrete specific guidance that is fully actionable, so not the score-2 'pseudocode/incomplete' case.

3 / 3

Workflow Clarity

A clear five-step sequence (Define Product → Specify Hooks → List Talking Points → Authenticity Guidelines → Output Brief) with explicit checklists; no validation/feedback loop is required because brief generation is neither destructive nor batch, so the score-2 cap for risky operations does not apply.

3 / 3

Progressive Disclosure

The skill is a single ~260-line file with a large (~150-line) output template inline and no bundle files or one-level-deep references; it is well-organized into sections but exceeds the under-50-line 'simple skill' exception, so it sits at the score-2 anchor of 'structure present but content that could be separate is inline' rather than the reference-split score-3 case.

2 / 3

Total

10

/

12

Passed

Description

100%

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 strong: concrete capabilities, natural trigger terms, explicit 'Use when...' guidance, and a distinct niche. It cleanly matches the top anchors on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions/components — 'product info, hook requirements, talking points, and authenticity guidelines' — matching the anchor for multiple specific concrete actions rather than the single-domain score-2 example.

3 / 3

Completeness

Explicitly answers both 'what' ('Create briefs for UGC creators including...') and 'when' ('Use when working with UGC creators, preparing creator packages, or scaling content production...'), matching the score-3 anchor; not the score-2 case where 'when' is only implied.

3 / 3

Trigger Term Quality

Natural domain terms a user would say are present — 'UGC creators', 'creator packages', 'content production' — giving good coverage rather than just one relevant keyword like the score-2 anchor.

3 / 3

Distinctiveness Conflict Risk

A clear niche (UGC creator briefs) with distinct triggers unlikely to conflict with other skills, matching the score-3 anchor; not generic enough to risk the score-2 overlap.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MODSetter/SurfSense
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.