CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-profound

Profound LLM citation tracker (extension). Time-series brand citation rates across ChatGPT, Perplexity, and other LLMs. Pairs with seo-seranking for triangulated AI visibility coverage.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./extensions/profound/skills/seo-profound/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 model of token-efficient routing-skill authoring: tight sections, exact commands, a crisp command table, explicit cross-skill boundaries, and a sensible untrusted-data security note, with no filler. The only gaps are the absence of worked API/usage examples and error-recovery steps, which keep actionability and workflow clarity at 4 rather than 5.

DimensionReasoningScore

Conciseness

The ~40-line body is lean: every section carries skill-specific facts Claude could not know (the Profound-vs-SE-Ranking polling distinction, the routing table, citation format "Profound (live, confidence 0.90)", delegation rules) with zero padding or explanation of concepts Claude already knows. It matches anchor 5 — every token earns its place — and is clearly above anchor 4's 'minor instances of over-explanation'.

5 / 5

Actionability

Concrete, runnable guidance dominates: "Run `extensions/profound/install.sh` or `install.ps1`", "check `~/.claude/settings.json` has `env.PROFOUND_API_KEY`", and four exact routing commands like "/seo profound citations <brand>" with defined outputs. It stops short of anchor 5 because there are no API-call examples, parameter details, or sample output shapes — the actual data-fetching mechanics are left to the extension.

4 / 5

Workflow Clarity

The flow is clearly sequenced: install → verify the API key ("Before any tool call, check `~/.claude/settings.json` has `env.PROFOUND_API_KEY`" is an explicit pre-flight checkpoint) → route via the command table → apply citation conventions → delegate. It misses anchor 5 because there is no error-recovery guidance (e.g., what to do when the key is missing or an API call fails), but checkpoints are present, keeping it above anchor 3.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (no references/, scripts/, or assets/ exist) and no need for external references, so per the rubric's simple-skill guideline well-organized sections alone qualify for 5. Sections (Prerequisites, Routing, Output conventions, Cross-skill delegation, Security) are clear, flat, and easy to navigate.

5 / 5

Total

18

/

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 identifies a clear niche (Profound's time-series LLM citation tracking) and distinguishes it from seo-seranking, but it is incomplete: it states what the skill does without any 'use when' trigger guidance, and it under-sells the skill's actual capabilities (prompts, competitors, alerts) relative to what the body delivers. It is serviceable but below the standard of the good examples, which pair capabilities with explicit trigger clauses.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about brand mentions or citations in ChatGPT, Perplexity, or other LLMs, or wants week-over-week/month-over-month AI visibility trends for a brand."

Enumerate the concrete capabilities the skill actually exposes — top prompts analysis, competitor citation tracking, and spike/drop alerts — instead of only "time-series brand citation rates".

Include natural synonym phrases such as "brand mentions" and "AI search visibility" so users phrasing the need differently still surface this skill over seo-seranking.

DimensionReasoningScore

Specificity

"Time-series brand citation rates across ChatGPT, Perplexity, and other LLMs" names the domain and one concrete capability, but the description stops there — it never mentions the prompts analysis, competitor citations, or spike/drop alerts the body shows, so coverage is not comprehensive. It is above anchor 2 (which names only a domain with generic actions) but does not list the several specific actions required for anchor 4.

3 / 5

Completeness

The 'what' is clearly stated ("Time-series brand citation rates across ChatGPT, Perplexity, and other LLMs"), but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description, capping completeness at 3 per the judging guidelines. It is not anchor 4 because the 'when' is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

Natural phrases a user would say are present — "citation", "brand citation rates", "ChatGPT", "Perplexity", "AI visibility" — giving good keyword coverage for this domain. It falls short of anchor 5 because common synonyms like "brand mentions", "AI search", or "how often LLMs cite us" are missing, but it is clearly above anchor 3's 'missing common variations' level since multiple natural terms appear.

4 / 5

Distinctiveness Conflict Risk

"Profound LLM citation tracker" names a specific vendor tool and "Pairs with seo-seranking for triangulated AI visibility coverage" explicitly delineates its role against the closest sibling skill, making it mostly distinct with only minor overlap risk against the other seo-* AI-visibility skills. It does not reach anchor 5 because no distinct trigger phrases are given and "AI visibility coverage" still overlaps conceptually with seo-seranking/seo-dataforseo.

4 / 5

Total

14

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

AgriciDaniel/claude-seo

Path

extensions/profound/skills/seo-profound/SKILL.md

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.