CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

63

Quality

79%

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 ./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 lean, well-structured routing skill: concrete commands, an explicit pre-call environment check, exact output conventions, and clear cross-skill delegation. Its only meaningful weakness is the absence of error-recovery guidance and sample outputs, which keeps actionability and workflow clarity at 4 rather than 5.

Suggestions

Add brief error-recovery guidance, e.g. what to do when PROFOUND_API_KEY is missing or a Profound API call fails (re-check settings, surface the error, fall back to seo-seranking for coverage).

Include one short sample output per routing command (e.g. a two-line example of the citation-rate + 30-day trend result) so the agent knows what to present.

DimensionReasoningScore

Conciseness

The ~35-line body is lean with no padding and no explanation of concepts Claude already knows; even the opening comparison ('Profound continuously polls and publishes time-series so trend deltas... are first-class') conveys non-obvious routing logic. Every section (Prerequisites, Routing, Output conventions, Cross-skill delegation) earns its tokens, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Concrete, executable guidance: exact install commands ('Run extensions/profound/install.sh or install.ps1'), a routing table with parameterized commands ('/seo profound citations <brand>'), an exact pre-call check ('check ~/.claude/settings.json has env.PROFOUND_API_KEY'), and an exact citation format ('Profound (live, confidence 0.90)'). Minor gaps: no sample output or example invocation per command, fitting 'mostly executable guidance with minor gaps' rather than fully copy-paste-ready coverage of common cases.

4 / 5

Workflow Clarity

A clear implied sequence (verify install/key/env, route via the command table, apply output conventions, delegate) with an explicit pre-call validation checkpoint on the API key. It falls short of the top anchor because there is no error-recovery guidance (e.g., what to do when the key is missing or an API call fails) — 'most checkpoints present; minor validation gaps.' No destructive or batch operations, so the cap-3 rule does not apply.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories), and the body is under 50 lines with no content that warrants external files; per the rubric's simple-skill guidance, well-organized sections alone earn the top score. Sections are clearly labeled, references (install.sh, sibling skills) are one level deep and clearly signaled.

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 is specific and well-differentiated, naming the tool, metric, and platforms concretely, but it lacks any explicit 'Use when...' trigger guidance, which caps completeness and keeps trigger-term quality from the top band. Adding a trigger clause naming common user phrasings (LLM citations, brand mentions in ChatGPT/Perplexity) would address the main gaps.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about brand mentions or citation rates in ChatGPT, Perplexity, or other LLMs, or wants AI visibility trends over time.'

Mention the additional capabilities the skill actually provides (top prompts, competitor co-citations, spike/drop alerts) so the 'what' is more comprehensive.

Include common synonyms such as 'brand mentions' and 'AI visibility' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Profound LLM citation tracker') and one-to-two concrete actions — 'Time-series brand citation rates across ChatGPT, Perplexity, and other LLMs' — with named platforms. It is not comprehensive: capabilities the body documents (prompts, competitors, alerts) are absent, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor rather than the 'several specific actions' anchor above.

3 / 5

Completeness

The 'what' is clear (time-series brand citation rates across LLMs, pairing with seo-seranking), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the judging guideline caps this dimension at 3 for a missing 'when'.

3 / 5

Trigger Term Quality

Natural keywords users would say are present: 'citation', 'brand citation rates', 'ChatGPT', 'Perplexity', 'time-series', 'AI visibility'. A few common variations are missing ('brand mentions', 'AI Overviews', 'share of voice', 'Gemini'), fitting the 'good keyword coverage; a few natural terms missing' anchor — above the generic keyword level, below comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The named tool (Profound), named platforms, and the explicit 'Pairs with seo-seranking for triangulated AI visibility coverage' carve out a distinct niche, giving it minor overlap risk with closely related AI-visibility skills rather than the minimal-conflict clarity of the top anchor, which would include explicit trigger phrasing.

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
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.