CtrlK
BlogDocsLog inGet started
Tessl Logo

ad-creative

Generate and iterate ad creative including headlines, descriptions, and primary text. Useful for paid social and search ad iteration.

51

Quality

56%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/ad-creative/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

43%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 well-organized, token-efficient catalogue stub, but as a skill it fails its core job: it contains no actual guidance for generating or iterating ad creative, deferring everything to an external GitHub repo with only a vague 'install the bundle' instruction. Structure and brevity are fine; actionability and workflow clarity are the weak points.

Suggestions

Replace the vague 'install the upstream bundle into your active agent's skills directory' with concrete steps or a copy-paste command (e.g., git clone with the target path and any install/verification commands).

Inline at least the core ad-creative workflow (headline/description/primary-text generation and iteration patterns, with a worked example) into SKILL.md or bundled reference files, instead of pointing everything to an external URL the agent cannot reliably act on.

Convert the 'How to use' section into a numbered sequence with an explicit invocation example and a check that the skill was actually loaded, so the agent can verify each step succeeded before invoking by name or trigger phrase.

DimensionReasoningScore

Conciseness

The ~25-line body is lean with no explanation of concepts Claude already knows, matching 'efficient; minor instances that could be trimmed'. It is not a 5 because the frontmatter description is repeated verbatim in 'What it does' and the upstream URL and category are restated in 'Source' — small duplications that don't earn their tokens.

4 / 5

Actionability

The only concrete instruction is a bash block containing "open https://github.com/coreyhaines31/marketingskills", and the key step — "install the upstream bundle into your active agent's skills directory" — is a high-level hint with no command, path, or procedure, matching the anchor 'minimal concrete guidance; high-level hints but missing the specific steps to execute'. It is not a 1 because there is at least one executable command and a concrete invocation mechanism (by name or trigger phrase).

2 / 5

Workflow Clarity

A rough sequence exists (inspect upstream README → install the bundle → invoke by name) but the critical middle step is undefined — how and where to install is never specified — matching 'rough sequence present but many gaps; steps poorly defined'. Not a 3 because the steps are not concretely listed with an executable form; the actual ad-creation workflow the skill advertises is never sequenced at all.

2 / 5

Progressive Disclosure

Sections (What it does / Source / How to use) are present and the single reference — the upstream repo URL — is one level deep and clearly signaled. It is not a 4 or 5 because all detailed material lives outside the bundle at an external URL rather than in bundled reference files, so the SKILL.md functions as a stub pointer rather than an overview over a real file structure (no references/, scripts/, or assets/ exist).

3 / 5

Total

11

/

20

Passed

Description

70%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 solid description: third-person, concise, with a clear 'what' and an explicit (if scenario-style) 'when' plus natural trigger vocabulary. The main gaps are limited action coverage beyond 'generate and iterate' and the absence of common trigger-phrase variations inside the description field itself.

DimensionReasoningScore

Specificity

"Generate and iterate ad creative including headlines, descriptions, and primary text" names the domain and two actions (generate, iterate) with three concrete deliverables, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. It is not a 4 because coverage stops there — no mention of iteration workflow, channels, formats, or testing, so several specific actions are absent.

3 / 5

Completeness

Both parts are present: 'what' is "Generate and iterate ad creative including headlines, descriptions, and primary text" and 'when' is "Useful for paid social and search ad iteration" — a clear what with an explicit when clause, mirroring the anchor-4 example. It is not a 5 because the 'when' states a scenario rather than concrete trigger phrases (e.g., 'Use when the user mentions ad copy or asks for ad variations'), and not a 3 because the when guidance is explicit, not merely implied.

4 / 5

Trigger Term Quality

The description itself carries natural terms users would say — "ad creative", "headlines", "primary text", "paid social", "search ad" — giving good keyword coverage. It is not a 5 because common variations like "ad copy", "ad variations", or platform names (Facebook/Google ads) appear only in the frontmatter triggers list, not in the description field.

4 / 5

Distinctiveness Conflict Risk

The niche is fairly clear — paid ad copy generation/iteration for social and search — so it is mostly distinct with only minor overlap risk against closely related general copywriting or marketing skills. It is not a 5 because 'generate... headlines, descriptions' could still collide with generic content-writing skills that don't have their own dedicated trigger terms.

4 / 5

Total

15

/

20

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.

Validation — 15 / 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
nexu-io/open-design
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.