CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

encyclopedia

Knowledge retrieval from multiple sources. Search docs, web, and code with intelligent routing, RRF fusion, circuit breakers, and semantic caching.

Quality

76%

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 ./encyclopedia/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 highly actionable — complete CLI invocations, options, outputs, configuration, and error codes — with a well-sequenced six-phase architecture and explicit degradation/fallback behavior. Its main weaknesses are dead references (constitution.md, SPEC.md, shared/feature_flags.py are missing from the bundle) and inline architecture detail that should live in the referenced files.

Suggestions

Ship the referenced "constitution.md" and "SPEC.md" in the bundle or remove the references; dead links break navigation and the Constitution section currently summarizes a file the reader cannot open.

Move the detailed per-phase architecture (Phase 1-5 internals, verbose JSON diagnostics) into SPEC.md and keep only the phase list and routing table in SKILL.md, deepening the progressive-disclosure split.

Reorder so setup precedes usage: put the required environment variables and credential-validation behavior before the command reference, forming an explicit configure-then-run workflow.

DimensionReasoningScore

Conciseness

The body is dense with skill-specific facts Claude could not know (thresholds, feature flags, CLI path overrides, error codes) with only minor trimmable padding — the "A billion pages, a billion facts" epigraph and the full verbose-JSON sample. It matches anchor 4 (efficient with minor over-explanation) rather than anchor 3, since almost all content is non-inferable configuration detail.

4 / 5

Actionability

Every command ships as a complete, copy-paste-ready invocation ("python3 scripts/encyclopedia.py search \"repo:anthropics/anthology describe auth middleware\""), with exhaustive options, example JSON outputs, env vars with defaults, and error codes. This matches anchor 5 (fully executable commands covering the common cases).

5 / 5

Workflow Clarity

The six-phase pipeline is explicitly sequenced, with a clear degradation hierarchy, circuit-breaker probe/recovery loop, and dry-run/verbose verification modes — matching anchor 4's "clear sequence with most checkpoints present". It falls short of anchor 5 because there is no ordered user-side workflow (environment setup and credential validation appear only after the commands) and no explicit validate-then-proceed checkpoint for the reader.

4 / 5

Progressive Disclosure

The body references "constitution.md", "SPEC.md", and "shared/feature_flags.py", none of which exist in the bundle, while inlining the full phase architecture that SPEC.md is supposed to hold — matching anchor 3 (references present but not cleanly resolvable; content that should be separate is inline). It is not anchor 2 because section structure is real and the referenced scripts (encyclopedia.py, source_health.py, semantic_cache.py, source_profiler.py, cgcli/, anime-mori/) all exist.

3 / 5

Total

16

/

20

Passed

Description

62%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, concrete capability (multi-source knowledge retrieval across docs, web, and code) but omits any "Use when..." trigger guidance, capping completeness. Natural keywords are present but lack common variations, and the broad search framing carries moderate conflict risk with other search-oriented skills.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to search or look something up across documentation, the web, or a codebase".

Include natural synonyms users would say ("look up", "find", "documentation", "API docs") alongside the existing "search/docs/web/code" terms.

Trim implementation jargon ("RRF fusion, circuit breakers, semantic caching") in favor of user-facing phrasing that distinguishes this from plain web-search skills.

DimensionReasoningScore

Specificity

"Search docs, web, and code" names three concrete retrieval targets, and "intelligent routing, RRF fusion, circuit breakers, and semantic caching" lists concrete mechanisms. It lists several specific actions with minor gaps (no lookup or code-analysis verbs), matching the anchor 4 example rather than anchor 5's comprehensive coverage or anchor 3's 1-2 actions.

4 / 5

Completeness

The "what" is clear ("Knowledge retrieval from multiple sources. Search docs, web, and code"), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not lower because the "what" is concrete and unambiguous.

3 / 5

Trigger Term Quality

"Search", "docs", "web", "code", and "knowledge retrieval" are natural terms a user would say, giving good keyword coverage. A few natural variations are missing ("look up", "find", "documentation", "API docs") and the trailing jargon ("RRF fusion, circuit breakers") is not user-spoken, so it sits between anchor 3 and anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Search docs, web, and code" is broad and would overlap with generic web-search, documentation-lookup, or code-search skills, matching anchor 3 ("somewhat specific but could still overlap with similar skills"). It is not anchor 4 because the domain terms lack a distinct niche trigger, and not anchor 2 because the multi-source retrieval framing is not entirely generic.

3 / 5

Total

14

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Raudbjorn/cognitive-construct

Path

encyclopedia/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.