CtrlK
BlogDocsLog inGet started
Tessl Logo

cli-hub-matrix-knowledge-research

Capability-based multi-tool matrix for research, note-taking, document authoring, and publishing. Agents compose providers (CLI-Anything harnesses, public CLIs, Python libs, native binaries, cloud APIs) per capability.

55

Quality

62%

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 ./cli-hub-matrix/knowledge-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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, actionable capability matrix with executable preflight tooling, a concrete consent template, and clear sequencing guidance. It scores well across all dimensions, with the main slack being recipes that list capabilities rather than detailed validated step sequences.

DimensionReasoningScore

Conciseness

The body is dense, information-rich provider tables with no padding and no explanations of concepts Claude already knows; the prose sections (constraints, suggest template, recipes, gaps, guidance) are all functional, with only minor trims possible.

4 / 5

Actionability

Provides an executable preflight block (importlib/command -v/env-var checks), concrete install/preflight commands, and a copy-paste suggest-to-user template; per-provider invocation is implied by name rather than shown, leaving a minor gap.

4 / 5

Workflow Clarity

Clear sequence (preflight → selection constraints → consent/escalation → capabilities → recipes) with real checkpoints (preflight validation, suggest/skip feedback loop, agent-guidance sequencing rules); the recipes themselves are capability lists without per-step validation.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with signaled one-level external references (the schema and matrix plan); no bundle files exist to offload to, and the inlined matrix is cohesive, though the per-capability tables could alternatively live in separate reference files.

4 / 5

Total

16

/

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 clearly states what the skill covers but omits any explicit 'when to use' trigger guidance, capping completeness. Natural trigger terms are present but diluted by technical jargon, and the broad four-domain scope raises moderate conflict risk.

Suggestions

Add an explicit 'Use when...' clause naming concrete user triggers (e.g., literature reviews, bibliographies, note-taking, writing or publishing documents) to lift completeness above 3.

Lead with the natural activity keywords users actually say and push the jargon ('CLI-Anything harnesses', 'compose providers per capability') later, improving trigger-term quality.

Narrow or sharpen the framing so it is distinguishable from a generic document- or research-handling skill.

DimensionReasoningScore

Specificity

Names the domain plus several activity areas ('research, note-taking, document authoring, and publishing') and a concrete action ('Agents compose providers ... per capability'), but the verbs are weak and it lacks a comprehensive list of concrete actions like 'extract/fill/merge'.

3 / 5

Completeness

Gives a clear 'what' (capability-based multi-tool matrix across four activity domains) but provides no 'Use when...' clause or equivalent trigger guidance; per the rubric guideline, a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant natural terms ('research, note-taking, document authoring, publishing') but they are embedded in heavy jargon ('multi-tool matrix', 'CLI-Anything harnesses', 'compose providers'), and common synonyms and file extensions are missing.

3 / 5

Distinctiveness Conflict Risk

The scope spans research, notes, documents, and publishing — broad enough to overlap with several single-domain skills — though the 'compose providers per capability' framing is somewhat distinctive.

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository
HKUDS/CLI-Anything
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.