CtrlK
BlogDocsLog inGet started
Tessl Logo

infinite-gratitude

Multi-agent research skill for parallel research execution (10 agents, battle-tested with real case studies).

44

Quality

45%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/infinite-gratitude/SKILL.md

The canonical home for this skill is infinite-gratitude in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

41%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 clean, lean stub that points externally, but as a SKILL.md it offers almost no executable or workflow guidance — the actual skill behavior lives outside the file. Conciseness and structure are good; actionability and workflow clarity are weak.

Suggestions

Inline the core usage workflow (how to launch the 10-agent research run and what it produces) instead of deferring entirely to the external repo.

Add a minimal executable example beyond `git clone`, e.g., the command or invocation that starts a research job.

Include a validation/synthesis checkpoint in the workflow since multi-agent research aggregates outputs that should be verified.

DimensionReasoningScore

Conciseness

The body is lean, does not explain concepts Claude already knows, and assumes competence; the only bloat is the Description section restating the frontmatter, a minor trim opportunity.

4 / 5

Actionability

The only executable command is `git clone` for acquisition; all actual usage guidance is deferred to an external repository ('Please refer to the official repository for installation and usage instructions'), leaving the specific steps to execute missing.

2 / 5

Workflow Clarity

Despite describing a 10-agent parallel research process, the body provides no sequenced steps or validation checkpoints — usage is entirely offloaded to an external repo.

1 / 5

Progressive Disclosure

Clear section headers (Description, When to Use, How to Use) with a single clearly signaled one-level external reference (the repo URL) and no local bundle to organize; it is a thin stub rather than genuinely split local content, so it stops short of 5.

4 / 5

Total

11

/

20

Passed

Description

50%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 states a clear capability (parallel multi-agent research with 10 agents) but lacks any explicit trigger guidance and uses some claim-style language. It sits at the midpoint across all dimensions.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases (e.g., 'Use when you need deep, parallelized research on a topic across many sources').

Replace the claim 'battle-tested with real case studies' with a concrete action or output the skill produces (e.g., 'synthesizes findings into a cited report').

Include natural synonyms users would say ('deep research', 'investigate a topic', 'literature review') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('multi-agent research skill') and a concrete action ('parallel research execution (10 agents)'), but 'battle-tested with real case studies' is a claim rather than an additional action and coverage is not comprehensive.

3 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'research' and 'case studies' are relevant natural terms, but 'parallel research execution' leans technical and common synonyms (deep research, investigate, literature review) are absent.

3 / 5

Distinctiveness Conflict Risk

'Multi-agent parallel research (10 agents)' is somewhat specific, but research is a broad category that overlaps with general/deep-research skills, so conflict risk remains.

3 / 5

Total

12

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.