CtrlK
BlogDocsLog inGet started
Tessl Logo

brief-generator

Use when the user asks to "create an influencer brief" or "write a campaign brief"; produces a structured creator brief with deliverables, key messages, creative direction, timeline, disclosure rules, and compensation terms. Not for choosing how to split spend across creators — use budget-optimizer. 达人合作简报/创作者BF

68

Quality

85%

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

70%Weight 40%Scale 1-3

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

The body is well-structured with a clear sequenced workflow, validation checkpoints, and clean progressive disclosure to real bundle files. Its weakest spots are mild redundancy in the sibling-skill listings and deferring the actual template specifics to references, which limits standalone actionability.

Suggestions

De-duplicate the sibling-skill list: keep it in one section (Reference Materials or Next Best Skill) and cross-reference from the other to remove repeated entries.

Trim the introductory value statement ('Good briefs lead to better content, fewer revisions, and stronger partnerships.') or fold it into the contract, since it states benefits Claude can already infer.

Inline a minimal skeleton of the master brief template (section headers + one example field) so the body is actionable without opening brief-templates.md, keeping the full variations in the reference.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes competence, but the intro value statement ('Good briefs lead to better content, fewer revisions...') is mild fluff and the sibling-skill list is repeated across 'Reference Materials' and 'Next Best Skill', so it could be tightened.

2 / 3

Actionability

Steps name concrete artifacts and markers (e.g. '[needs source]', 'operation: propose', registry-events.py), but the actual master fill-in template and variation tables are deferred to referenced files rather than given inline, leaving key specifics incomplete in the body.

2 / 3

Workflow Clarity

A clear four-step numbered sequence is paired with a 'Done when' checklist and an explicit validation/fallback loop (claims context-valid or 'visibly blocked', dependency_status verified | approved-fallback | blocked), matching the anchor for explicit checkpoints and feedback loops.

3 / 3

Progressive Disclosure

The body is an overview that points to one-level-deep, clearly signaled references; both local bundle files (brief-templates.md, creator-voice-intake.md) exist and are linked with descriptions, giving easy navigation without nested-reference chains.

3 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, trigger-rich, complete, and explicitly scoped against a sibling skill, hitting the top anchor on every dimension. It avoids vague fluff and uses the accepted 'Use when...' trigger pattern rather than first/second person voice.

DimensionReasoningScore

Specificity

Enumerates multiple concrete brief components — 'deliverables, key messages, creative direction, timeline, disclosure rules, and compensation terms' — matching the anchor that lists several specific concrete items rather than a vague domain label.

3 / 3

Completeness

States both what ('produces a structured creator brief with...') and when via an explicit 'Use when the user asks to...' clause, satisfying the top anchor for both what and when.

3 / 3

Trigger Term Quality

Quotes natural phrasings a user would say — 'create an influencer brief' and 'write a campaign brief' — plus 'influencer brief'/'campaign brief' and localized terms, giving good coverage of likely trigger language.

3 / 3

Distinctiveness Conflict Risk

Includes an explicit negative boundary — 'Not for choosing how to split spend across creators — use budget-optimizer' — carving a clear niche unlikely to trigger the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

75%

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

Validation12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

relative_links

Relative link issues: 15 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository
aaron-he-zhu/aaron-marketing-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.