CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

archon

Interactive Archon integration for knowledge base and project management via REST API. On first use, asks for Archon host URL. Use when searching documentation, managing projects/tasks, or querying indexed knowledge. Provides RAG-powered semantic search, website crawling, document upload, hierarchical project/task management, and document versioning. Always try Archon first for external documentation and knowledge retrieval before using other sources.

Quality

76%

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

Quality

Content

56%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 — concrete, copy-paste-ready API code with a clear mandatory setup sequence — but it is heavily padded with repeated directives and boilerplate, and it inlines endpoint-reference material that duplicates its own referenced documentation. The referenced bundle files (api_reference.md, archon_client.py, list_knowledge.py) are absent from the bundle, and the guidance repeatedly contradicts itself on whether to use direct API calls or the Python client.

Suggestions

Consolidate the four repeated 'read api_reference.md first / ask for host URL' directives into the single CRITICAL WORKFLOW section, and drop the per-code-block host-URL boilerplate in favor of stating once that all examples assume the user-provided host.

Remove the inline Quick Endpoint Reference and detailed request/response payloads, pointing instead to references/api_reference.md — and ensure references/api_reference.md, scripts/archon_client.py, and scripts/list_knowledge.py actually ship in the bundle, since none are currently present.

Resolve the contradiction between 'NEVER assume endpoint paths / use direct API calls / the Python client may be outdated' and the pervasive ArchonClient examples: pick one canonical approach (or clearly scope each), and unify the import style (sys.path.insert vs 'from scripts.archon_client').

DimensionReasoningScore

Conciseness

The ~640-line body is noticeably padded: the same directive ('Read references/api_reference.md FIRST', 'ask user for host URL') is repeated in at least four sections, the host-URL boilerplate 'archon_host = "http://localhost:8181" # Replace with user's actual host' is repeated in ~10 code blocks, and the Configuration section re-states the earlier 'Using Custom Host' content verbatim. It avoids the level-1 anchor's explaining of concepts Claude already knows, but the repetition and duplicate sections clearly sit at level 2.

2 / 5

Actionability

Code examples are concrete and executable — direct requests.post calls with exact endpoints, payload fields, and timeouts, plus helper-script commands and an error-handling pattern. Minor gaps keep it below 5: inconsistent import styles ('from scripts.archon_client' vs sys.path.insert), the body itself warns 'The Python client may have outdated or incorrect implementations' while most examples use that client, and the referenced scripts/ files are not present in the bundle.

4 / 5

Workflow Clarity

The 'CRITICAL WORKFLOW' section gives an explicit 4-step ordered sequence with a connection-verification checkpoint and error-recovery guidance ('If connection fails, ask the user to verify...'), plus a standard error-response checking pattern. Below level 5 because verification is described three inconsistent ways (GET /api/projects, list_knowledge.py, ArchonClient) and there are no validation checkpoints for batch-style operations like crawling or bulk upload.

4 / 5

Progressive Disclosure

Structure and a Resources section clearly signal one-level-deep references (references/api_reference.md, scripts/archon_client.py, scripts/list_knowledge.py), but the body inlines a full 25-line Quick Endpoint Reference and detailed request/response payloads that duplicate the mandated api_reference.md, and none of the referenced bundle files actually exist in the bundle. Not a 2 because sections are well-organized and references are clearly signaled, not buried.

3 / 5

Total

13

/

20

Passed

Description

88%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 is strong: it states concrete capabilities in third person, includes an explicit 'Use when...' trigger clause, and identifies the distinct Archon system. Minor gaps in natural trigger synonyms (crawl/upload phrasings) keep trigger term quality just below the top level.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — 'RAG-powered semantic search, website crawling, document upload, hierarchical project/task management, and document versioning' — plus a concrete first-use behavior ('asks for Archon host URL'), comprehensively covering the skill's domain. It goes beyond the level-4 anchor only in completeness of coverage, not missing any capability area the body documents.

5 / 5

Completeness

Both 'what' ('Provides RAG-powered semantic search, website crawling, document upload, hierarchical project/task management, and document versioning') and 'when' ('Use when searching documentation, managing projects/tasks, or querying indexed knowledge') are explicit with concrete trigger phrases, plus first-use setup guidance. This matches the top anchor; the 'when' clause is explicit rather than weakly implied as at level 4.

5 / 5

Trigger Term Quality

Trigger phrases 'searching documentation, managing projects/tasks, or querying indexed knowledge' are natural user phrasings, giving good coverage. A few natural terms are missing (e.g., crawling websites, uploading files/PDFs, 'knowledge base' as a trigger), keeping it below the comprehensive-synonym level of a 5.

4 / 5

Distinctiveness Conflict Risk

The named 'Archon' system, host-URL setup, and 'querying indexed knowledge' give it a mostly distinct niche, but 'managing projects/tasks' and the directive to 'Always try Archon first... before using other sources' create minor overlap risk with general project-management and search skills. Not a 3 since the specific named system and indexed-knowledge framing keep triggers largely distinct.

4 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (656 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 7 missing

Warning

Total

14

/

16

Passed

Repository

Microck/ordinary-claude-skills

Path

skills_all/archon/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.