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.

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/marketing-ideas/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

59%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 skill provides a well-structured marketing prioritization framework with a concrete scoring system (MFS) and clear output format. Its main strengths are the actionable scoring formula and the disciplined workflow constraints. However, the critical weakness is the entirely missing '140 idea library' which is the core reference material, and some verbosity in framing sections that explain Claude's role rather than providing actionable content.

Suggestions

Include the 140 idea library in a separate bundle file (e.g., IDEA_LIBRARY.md) and properly reference it, or inline a representative subset—the current placeholder makes the skill incomplete.

Trim the introductory framing paragraphs (lines about 'Your role is not to brainstorm endlessly') which tell Claude what it already understands from the workflow steps.

Add a feedback loop step: what should happen when the user challenges a score or provides new constraints that change feasibility assessments.

DimensionReasoningScore

Conciseness

The skill is reasonably structured but includes some unnecessary framing (e.g., 'Your role is not to brainstorm endlessly', explaining what MFS stands for repeatedly, the 'When to Use' section at the end). The stage-based biases and guardrails sections are efficient, but the overall document could be tightened—particularly the introductory paragraphs and the verbose output format example.

3 / 5

Actionability

The MFS formula is concrete and executable, the scoring table is clear, and the output format example is specific and copy-paste ready. However, the '140 idea library' is referenced but entirely omitted ('omitted here for brevity but assumed intact'), which is a significant gap—the core reference material is missing. The workflow steps (establish context, shortlist, score, operationalize) are clear but somewhat high-level.

4 / 5

Workflow Clarity

The four-step workflow (establish context → shortlist → score → operationalize) is clearly sequenced with explicit constraints (never recommend MFS ≤ 0, max 5 ideas). The scoring formula and interpretation table serve as validation checkpoints. Minor gap: no explicit feedback loop for when the user disagrees with scoring or wants to re-evaluate with different constraints.

4 / 5

Progressive Disclosure

The skill references a '140 idea library' that is entirely absent with no bundle files provided, making the core reference material inaccessible. Section 8 references related skills but there are no bundle files to support them. The content that should be in separate files (the idea library) is neither inlined nor properly linked—it's just missing.

2 / 5

Total

13

/

20

Passed

Description

53%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 identifies a clear domain (SaaS marketing) and a unique mechanism (feasibility scoring), but lacks explicit trigger guidance and comprehensive action listing. It would benefit from a 'Use when...' clause and more specific capability enumeration to help Claude reliably select it from a large skill set.

Suggestions

Add a 'Use when...' clause with trigger terms like 'marketing plan', 'growth strategy', 'customer acquisition', 'go-to-market', or 'how to grow my SaaS'.

List specific actions such as 'recommends marketing channels, scores strategies by feasibility, suggests growth experiments, prioritizes tactics by effort and impact'.

Include common synonyms and related terms users might say: 'GTM strategy', 'user acquisition', 'startup marketing', 'product-led growth'.

DimensionReasoningScore

Specificity

Names the domain (marketing strategies for SaaS) and mentions a concrete mechanism (marketing feasibility scoring system), but doesn't list specific actions like 'generate channel recommendations', 'analyze competitors', or 'create growth plans'.

3 / 5

Completeness

Has a clear 'what' (provide marketing strategies and growth ideas with a scoring system) but no explicit 'when' clause. There's no 'Use when...' guidance to help Claude know when to select this skill.

3 / 5

Trigger Term Quality

Includes relevant keywords like 'marketing strategies', 'growth ideas', 'SaaS', and 'software products', but misses common user phrases like 'how to grow', 'customer acquisition', 'go-to-market', 'GTM', 'marketing plan', or 'growth hacking'.

3 / 5

Distinctiveness Conflict Risk

The combination of SaaS/software focus and the marketing feasibility scoring system makes it fairly distinct. Minor overlap risk with general business strategy or marketing skills, but the SaaS specificity and scoring system help differentiate it.

4 / 5

Total

13

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

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.