CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-seekers

-Automatically convert documentation websites, GitHub repositories, and PDFs into Claude AI skills in minutes.

45

Quality

47%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/skill-seekers/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

33%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 token-light and sectioned but substantively empty: it restates the description as filler, provides zero executable guidance or sequenced workflow, and offloads everything to an external repository link.

Suggestions

Replace the filler Instructions section with concrete, executable steps for the conversion process (e.g., fetch the source, parse/extract content, structure into SKILL.md + references, validate the bundle).

Add an explicit numbered workflow with validation checkpoints, since converting sources into skills is a multi-step operation prone to format errors.

Stop repeating the description fragment verbatim in each section; either give each section real content or remove the empty sections.

DimensionReasoningScore

Conciseness

The body is short and does not over-explain concepts Claude already knows, but it repeats the same description fragment verbatim across three sections, so a few tokens do not earn their place; this fits the "efficient with minor trimmable redundancy" anchor rather than the lean 5.

4 / 5

Actionability

There is no concrete code, command, or executable step anywhere; the Instructions section only says it "provides guidance and patterns for [description fragment]" and links an external repo, matching the entirely-vague/no-instruction anchor.

1 / 5

Workflow Clarity

A docs/repo/PDF-to-skill conversion is inherently multi-step, yet the body lists no sequenced steps and no validation checkpoints, so it matches the missing/incoherent-steps anchor.

1 / 5

Progressive Disclosure

The body is under 50 lines with clearly headed sections (Overview, When to Use, Instructions) and a single clearly signaled external link, which is good structure with only minor organization gaps; no local bundle files exist to evaluate one-level-deep references.

4 / 5

Total

10

/

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 conveys a clear, distinctive purpose with reasonable natural trigger terms, but it omits any explicit "when to use" guidance and offers only one high-level action, capping completeness and specificity.

Suggestions

Add an explicit "Use when ..." clause naming the trigger scenarios (e.g., "Use when the user wants to turn a docs site, repo, or PDF into a reusable Claude skill").

Expand beyond the single verb "convert" to list concrete actions such as fetching, parsing, structuring, and packaging output as a skill bundle.

Remove the leading "-" artifact and the "in minutes" fluff so the description reads cleanly in third person.

DimensionReasoningScore

Specificity

The description names three concrete input domains ("documentation websites, GitHub repositories, and PDFs") and one action ("convert ... into Claude AI skills"), but offers only that single action with no detail on how, matching the anchor for one clear action without comprehensive coverage. The leading "-" and "in minutes" add no specificity.

3 / 5

Completeness

It clearly states what the skill does but provides no "Use when ..." trigger clause, so per the rubric a missing explicit "when" caps completeness at 3.

3 / 5

Trigger Term Quality

It surfaces natural terms a user would actually say ("documentation websites", "GitHub repositories", "PDFs", "Claude AI skills"), giving good keyword coverage, though it omits common synonyms and file extensions that would push it to 5.

4 / 5

Distinctiveness Conflict Risk

The niche of converting docs/repos/PDFs into Claude skills is fairly distinct with limited overlap risk, but the absence of explicit trigger phrases keeps it just below the minimal-conflict anchor of 5.

4 / 5

Total

14

/

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.