CtrlK
BlogDocsLog inGet started
Tessl Logo

marketing-ideas

Provide proven marketing strategies and growth ideas for SaaS and software products, prioritized using a marketing feasibility scoring system.

57

Quality

66%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/marketing-ideas/SKILL.md

The canonical home for this skill is marketing-ideas in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 content is well-structured and actionable with a concrete scoring framework, but it is undermined by a missing idea library that is referenced but not provided, plus minor redundancy and a filler closing line.

Suggestions

Provide the 140-idea library as an actual bundle file (e.g. references/ideas.md) and link to it explicitly from Section 4 instead of stating it is 'assumed intact in file'.

Remove the redundant Guardrails restatements that duplicate Sections 1 and 3, or consolidate them into a single concise checklist.

Replace the generic 'When to Use' line with concrete trigger conditions or delete it, since the description already fails to carry that load.

DimensionReasoningScore

Conciseness

The body is largely lean — bullets, tables, and a formula rather than prose explaining concepts Claude already knows — but the Guardrails section restates rules already in sections 1 and 3, and the closing 'When to Use' line ('applicable to execute the workflow or actions described in the overview') is filler that could be trimmed.

4 / 5

Actionability

Concrete, executable guidance throughout: an explicit MFS formula, 1–5 scoring dimensions, an interpretation-to-action table, a worked numeric example, and a copy-paste output template; the main gap is that the referenced 140-idea library is not actually present, so Claude cannot select from ideas that are not supplied.

4 / 5

Workflow Clarity

Section 1 lays out a clear four-step sequence (establish context → shortlist → score → operationalize) with substeps, and the interpretation table acts as decision rules; no explicit validate-and-retry checkpoints, but none are required for this advisory, non-destructive task.

4 / 5

Progressive Disclosure

Sections are well-organized with clear headers, but the skill references a 140-idea library 'assumed intact in file' with no such file present (no references/ or assets/ bundle exists), and 'Related Skills' lists skills whose existence is unverified — a broken/dangling reference that undermines navigation.

3 / 5

Total

15

/

20

Passed

Description

61%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 clearly conveys the skill's purpose and domain with decent trigger terms, but it omits any explicit 'Use when...' guidance, which caps completeness and limits its ability to act as a reliable trigger.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g. 'Use when the user asks for marketing ideas, growth strategies, or go-to-market tactics for a SaaS or software product').

Replace abstract verbs ('provide', 'prioritized') with more concrete operations (e.g. 'selects, scores, and ranks marketing ideas') to lift specificity.

Broaden trigger term coverage with synonyms users actually say ('growth marketing', 'go-to-market', 'marketing tactics').

DimensionReasoningScore

Specificity

Names the domain ('marketing strategies and growth ideas for SaaS and software products') and two actions ('provide... strategies and growth ideas' and 'prioritized using a marketing feasibility scoring system'), but the actions are somewhat abstract and coverage is not comprehensive — not at the level of multiple concrete operations like the anchor-5 example.

3 / 5

Completeness

It clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural user-facing terms ('marketing strategies', 'growth ideas', 'SaaS', 'software products') that a user would plausibly say, though common synonyms like 'go-to-market', 'growth marketing', or 'marketing tactics' are missing.

4 / 5

Distinctiveness Conflict Risk

The SaaS/software marketing niche combined with an explicit feasibility-scoring system is mostly distinct with only minor overlap risk against generic marketing or growth skills.

4 / 5

Total

14

/

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.

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
administrakt0r/AI-Agents-Safe-Coding-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.