CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-pagerank-analyzer

Agent skill for pagerank-analyzer - invoke with $agent-pagerank-analyzer

37

9.44x
Quality

7%

Does it follow best practices?

Impact

85%

9.44x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-pagerank-analyzer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

14%

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

This skill is excessively verbose and reads more like a marketing brochure or capability catalog than actionable instructions. While it includes some useful MCP tool call examples with concrete parameters, the majority of the content consists of vague bullet-point lists describing capabilities, application domains, and integration patterns that provide no executable guidance. The skill would benefit enormously from being reduced to ~20% of its current size, focusing only on the MCP tool signatures, concrete usage examples, and clear workflows.

Suggestions

Remove all descriptive capability lists (Core Capabilities, Advanced Graph Algorithms, Application Domains, Performance Optimization, Integration Patterns) and replace with only the concrete MCP tool call examples that Claude needs.

Make code examples fully executable by replacing undefined helper functions with actual implementations or removing them entirely, showing only the MCP tool invocations with realistic parameters.

Add explicit validation checkpoints to workflows, e.g., 'Verify PageRank scores sum to ~1.0' or 'Check convergence by comparing iteration deltas', especially for the multi-step example workflows.

Split advanced integration patterns (Flow Nexus, Neural Graph Networks) into separate referenced files if they are needed, keeping SKILL.md as a concise overview with the core MCP tool usage.

DimensionReasoningScore

Conciseness

Extremely verbose with extensive bullet-point lists of capabilities, application domains, and integration patterns that Claude already knows or that provide no actionable guidance. Sections like 'Application Domains', 'Performance Optimization', and 'Advanced Graph Algorithms' are purely descriptive catalogs that waste tokens without teaching Claude anything new.

1 / 3

Actionability

Includes several code examples with MCP tool calls that show concrete parameters and usage patterns, which is useful. However, many examples use undefined helper functions (e.g., `extractTopRecommendations`, `identifyInfluencers`, `load_graph_partition`) making them not truly executable, and large sections are vague bullet-point descriptions rather than concrete instructions.

2 / 3

Workflow Clarity

The 'Example Workflows' section lists high-level steps like 'Build social network graph from user interactions' and 'Optimize influence campaign based on network analysis' without any concrete commands, validation checkpoints, or error recovery steps. These are abstract descriptions, not actionable workflows.

1 / 3

Progressive Disclosure

The content is a monolithic wall of text with no references to external files and no bundle files to support it. Everything is inlined in a single massive document with no clear hierarchy or navigation structure, making it difficult to find relevant information quickly.

1 / 3

Total

5

/

12

Passed

Description

0%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an extremely weak description that functions more as an invocation instruction than a skill description. It fails on every dimension: it describes no capabilities, includes no trigger terms, provides no guidance on when to use it, and offers no distinguishing information. The description needs to be completely rewritten.

Suggestions

Describe what the skill actually does with concrete actions, e.g., 'Analyzes link structures and computes PageRank scores for web pages or graph nodes, identifies most authoritative pages, and visualizes link relationships.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about page ranking, link analysis, graph centrality, website authority, SEO link structure, or computing importance scores in a network.'

Remove the invocation syntax ('invoke with $agent-pagerank-analyzer') from the description field, as this is operational metadata that doesn't help Claude decide when to select this skill.

DimensionReasoningScore

Specificity

The description provides no concrete actions whatsoever. It only names a tool ('pagerank-analyzer') without describing what it does. 'Agent skill for' is completely vague.

1 / 3

Completeness

Neither 'what does this do' nor 'when should Claude use it' is answered. The description only provides invocation syntax ('invoke with $agent-pagerank-analyzer') which is operational metadata, not a functional description.

1 / 3

Trigger Term Quality

The only potentially relevant keyword is 'pagerank' embedded in the tool name, but there are no natural user-facing trigger terms like 'page rank', 'link analysis', 'graph ranking', 'SEO', or any other terms a user might naturally use.

1 / 3

Distinctiveness Conflict Risk

While 'pagerank' in the name hints at a niche, the description itself is so generic ('Agent skill for...') that it provides no meaningful differentiation. Claude would have no basis to select this skill over others.

1 / 3

Total

4

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
ruvnet/ruflo
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.