CtrlK
BlogDocsLog inGet started
Tessl Logo

opensourcefaq

Answer open-source product questions by combining local source-code and documentation research, project framework notes generated by init, DeepWiki repository knowledge, and current web evidence, then save a sourced, diagram-rich Markdown answer to the current project's markdown directory. Use when the user asks about behavior, architecture, internals, configuration, APIs, troubleshooting, performance, operations, extension points, practical reproduction, or version-specific details of one or more open-source projects and provides the question, all relevant local source directories, and DeepWiki repoName values.

69

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, actionable skill body with explicit validation checkpoints and clean sectioning. The only notable gaps are minor verbosity in the bilingual article template and the absence of a worked end-to-end example.

Suggestions

Provide one short worked Mermaid snippet (e.g. a sequence or flow diagram) so the 'diagram-rich' requirement has a concrete syntax example to follow.

Consolidate the overlapping reproduction guidance between the Workflow step 5, the Practical Reproduction Requirements section, and the 实操示例 template heading to reduce repetition.

Consider moving the bilingual Article Structure template into a references file and linking to it, keeping SKILL.md as a leaner overview.

DimensionReasoningScore

Conciseness

Mostly efficient procedural guidance that assumes Claude's competence with no concept padding, but the bilingual Article Structure template and some overlap between Workflow, Practical Reproduction, and Validation sections could be trimmed.

4 / 5

Actionability

Provides concrete executable commands (rg, git -C rev-parse, markdown/opensourcefaq-<topic>.md) and a copy-paste markdown skeleton, with the minor gap of no fully worked example article or Mermaid syntax sample.

4 / 5

Workflow Clarity

A clear six-step sequence with an explicit verification step, feedback-loop language ('If a claim cannot be verified, mark it as an inference'), and a Validation Rules checklist for a multi-source batch research operation.

5 / 5

Progressive Disclosure

Self-contained skill with no bundle files, organized into clearly signaled sections (Overview, Inputs, Workflow, Practical Reproduction Requirements, Article Structure, Validation Rules) for easy navigation.

5 / 5

Total

18

/

20

Passed

Description

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

A strong, specific description that clearly states what the skill does and when to use it, with rich natural trigger terms and concrete required inputs. Minor overlap risk and a slightly broad trigger list keep it just below a perfect score.

Suggestions

Tighten the trigger list by grouping near-synonyms (e.g. behavior/architecture/internals) to reduce overlap risk with general code-explanation skills.

Add one or two common-synonym trigger phrasings (e.g. 'how does X work', 'why does X behave this way') that users would naturally say.

Name one more distinct output action beyond 'research + save markdown' (e.g. 'compare versions', 'generate reproduction steps') to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions (combining local source/docs research, DeepWiki knowledge, web evidence, then saving a sourced diagram-rich Markdown answer) with only minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both what (answer open-source product questions via multi-source research and save a sourced diagram-rich Markdown answer) and when (a 'Use when...' clause with concrete trigger phrases and required inputs).

5 / 5

Trigger Term Quality

Strong natural trigger coverage (behavior, architecture, internals, configuration, APIs, troubleshooting, performance, operations, extension points, practical reproduction, version-specific details) though missing some synonyms and file-extension-style variants.

4 / 5

Distinctiveness Conflict Risk

The local-source + DeepWiki + save-to-markdown niche is distinctive, though the broad trigger list (architecture/APIs/troubleshooting/performance) creates minor overlap risk with general code-research skills.

4 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
digoal/blog
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.