CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deeptutor-cli

Configure, manage, and use DeepTutor through its CLI, including capabilities, knowledge bases, partners, memory, sessions, notebooks, providers, skills, and the server or Web app.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 an unusually actionable CLI reference: concrete, executable commands with flags and formats, real validation checkpoints, and honest caveats about verification. Its main weaknesses are duplicated command listings and inline version-history details that bloat tokens, and a progressive-disclosure structure whose key referenced guides (docs-for-dev/*) are missing from the bundle, breaking navigation for the most critical setup path.

Suggestions

Ship the referenced docs-for-dev files (README.md, AGENT_SETUP.md, MODULES.md) in the bundle or inline their essential setup/troubleshooting steps, since these links are currently dead and carry the skill's most important guidance.

Deduplicate the 'Agent Setup' and 'System' blocks (config show/providers/apply, init, doctor appear in both) into a single section.

Move release-specific details (1.7.0 vs 1.6.15 upgrade paths, the TutorBot rename) into a reference file or a clearly labeled versions/deprecations section to keep the body version-stable.

DimensionReasoningScore

Conciseness

The body is fundamentally a lean command reference with no concept over-explanation, but it can be tightened: the config/init/doctor commands appear nearly verbatim in both 'Agent Setup' and 'System' sections, and time-sensitive version specifics ('1.7.0 modular release', 'upgrading from 1.6.15', 'the former TutorBot') sit inline rather than in a deprecated/old-patterns section. This fits anchor 3 (mostly efficient, some unnecessary content) better than anchor 4's minor-trimming level.

3 / 5

Actionability

Nearly every section is copy-paste-ready CLI syntax with flags, formats, and comments ('deeptutor kb create <name> --doc file.pdf', 'deeptutor run deep_question "Thermodynamics" --kb physics --config num_questions=5'), plus working discovery commands ('deeptutor plugin list', '--help') where static lists would go stale. Common cases are covered by the workflows section, matching anchor 5.

5 / 5

Workflow Clarity

The first-time setup workflow has a real sequence with explicit checkpoints ('python -m pip check', 'deeptutor module list', 'doctor --online', 'config apply --check') and honest readiness guidance ('Saving settings is not proof of readiness'), and destructive commands note confirmation ('--force/-f Skip confirmation'). It falls short of anchor 5 because error-recovery/feedback loops are delegated to the referenced setup guide rather than stated, and the daily workflows are single-command snippets without checkpoints.

4 / 5

Progressive Disclosure

The body is well-sectioned and its references are clearly signaled as one-level markdown links ([AGENT_SETUP.md], [MODULES.md]), but scored against the actual bundle those targets do not exist — there is no docs-for-dev/ or references/ directory — so the primary setup/troubleshooting path is a dead link, while unreferenced bundle content (assets/ localized READMEs, most scripts) is undiscoverable. This matches anchor 3 (structure present, organization/reference gaps) rather than anchor 4's 'minor organization gaps'.

3 / 5

Total

15

/

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 clearly names the product and comprehensively enumerates its subsystems, giving it a distinct trigger via the DeepTutor brand. However, it lacks any explicit 'when to use' trigger clause and relies on generic verbs (configure/manage/use) rather than concrete actions. Adding a 'Use when...' sentence with natural trigger phrases would materially improve it.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants to set up, configure, or troubleshoot DeepTutor, chat or run a capability (deep solve, quiz, research), or manage its knowledge bases, partners, or sessions."

Replace generic umbrella verbs with one or two concrete actions per subsystem (e.g., 'creates and searches knowledge bases', 'runs deep_solve and deep_research capabilities').

Add a natural synonym or two users might say ('tutoring', 'learning platform') to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

The verbs are generic umbrellas ("Configure, manage, and use DeepTutor through its CLI") rather than concrete actions, though the enumerated objects ("capabilities, knowledge bases, partners, memory, sessions, notebooks, providers, skills, and the server or Web app") give broad scope. This matches anchor 3 (domain named, actions not concrete/comprehensive) better than anchor 4, which requires several specific distinct actions like 'extracts text, fills forms'.

3 / 5

Completeness

The 'what' is clear (configure/manage/use DeepTutor CLI across enumerated subsystems) but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. It is not a 4 because 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural terms users would say are present: the product name "DeepTutor", "CLI", "knowledge bases", "skills", "sessions", "notebooks", "server or Web app". A few natural variations are missing (e.g., 'tutoring', 'learning platform', 'quiz', 'study'), matching anchor 4 (good coverage, a few natural terms missing) rather than anchor 5's synonym/extension completeness.

4 / 5

Distinctiveness Conflict Risk

The distinct product name "DeepTutor" gives a clear niche with distinct triggers, but generic nouns like "skills", "memory", and "server" create minor overlap risk with other skills covering those topics. This fits anchor 4 (mostly distinct, minor overlap) better than anchor 5's minimal-conflict example.

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 missing

Warning

Total

15

/

16

Passed

Repository

HKUDS/DeepTutor

Path

SKILL.md

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.