CtrlK
BlogDocsLog inGet started
Tessl Logo

competitor-prompt-hijacker

Use this skill whenever a user wants to win AI citations on prompts that competitors currently dominate — whether they say "competitors are getting cited instead of us", "we're losing on these prompts", "how do I outrank [competitor] in AI answers", "find prompts where we should be winning", "create content to beat [competitor]", or any variation where the goal is capturing AI share on prompts a competitor currently owns. This skill pulls competitor visibility data from AI Visibility, identifies the specific prompts where competitors win and Amplitude is absent, clusters them by intent, and produces targeted comparison pages, alternatives content, or rebuttal assets — then pushes drafts to CMS. Trigger on any mention of competitor, prompt hijack, outrank, or "why is [competitor] getting cited instead of us".

68

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

A strongly actionable, well-sequenced workflow skill held back by its monolithic single-file structure, some tighten-able prose, and the absence of an explicit validation checkpoint before the CMS push. Actionability is the clear strength; progressive disclosure and workflow gates are the main weaknesses.

Suggestions

Add an explicit validation/verification checkpoint in Step 6 before/after the CMS push (e.g., confirm the draft ID resolved, review the rendered draft, and a retry path if the create call fails) to lift workflow_clarity.

Trim orientation prose in the intro and the 'What makes competitor content get cited' section — the tables and step instructions already carry the guidance Claude needs.

Split the per-bucket content templates (Step 5) and the per-CMS push instructions (Step 6) into reference files linked from SKILL.md so the body serves as a lean overview with one-level-deep references.

DimensionReasoningScore

Conciseness

Mostly efficient — specific tool names, thresholds, and tables earn their place — but orientation prose ("the answer it gives is determined by what's been written", "This avoids a copy-paste dead end") and the closing principles section could be tightened without losing guidance.

2 / 3

Actionability

Highly concrete: named tool calls (get_ai_visibility_competitors, get_ai_visibility_prompts, web_fetch, create_documents_from_markdown, etc.), specific fields, numeric thresholds (above 50% / below 30%), and full per-bucket content templates with H1 wording and section structures.

3 / 3

Workflow Clarity

Steps 0–6 are clearly sequenced with selection gates, but there is no explicit validation/verification or error-recovery feedback loop before the outward-facing CMS push, which the rubric caps at 2 for batch/outward operations.

2 / 3

Progressive Disclosure

Well organized into labeled sections but monolithic — all content is inline in a single ~250-line SKILL.md with no bundle files; the per-bucket templates and per-CMS push instructions are content that could plausibly be split into references.

2 / 3

Total

9

/

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.

An exemplary description: concrete third-person actions, rich natural-language triggers, and explicit what-and-when guidance all present. Voice is correctly third person throughout, so no specificity penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in third person: "pulls competitor visibility data from AI Visibility, identifies the specific prompts where competitors win and Amplitude is absent, clusters them by intent, and produces targeted comparison pages, alternatives content, or rebuttal assets — then pushes drafts to CMS."

3 / 3

Completeness

Explicitly answers both: what it does (the pull/cluster/produce/push pipeline) and when to use it ("Use this skill whenever a user wants to win AI citations..." and the closing "Trigger on any mention of competitor, prompt hijack, outrank...").

3 / 3

Trigger Term Quality

Strong coverage of natural user phrasings — "competitors are getting cited instead of us", "we're losing on these prompts", "how do I outrank [competitor]", "create content to beat [competitor]", plus the trigger line "prompt hijack, outrank, or 'why is [competitor] getting cited instead of us'".

3 / 3

Distinctiveness Conflict Risk

A clear, narrow niche (hijacking competitor-owned AI-citation prompts for Amplitude) with distinctive triggers unlikely to fire for unrelated skills.

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
amplitude/builder-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.