CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wiki-history-ingest

Route generic agent-history ingestion requests to the appropriate specialized history-ingest skill. Use when the user asks to ingest AI-agent history without directly selecting the underlying agent-specific skill.

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary thin-router skill body: exact dispatch table, concrete path-based heuristics, an explicit clarification fallback, and clean boundaries against the destination skills and wiki-ingest. The only improvement is trimming the partially duplicative examples list.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — a dispatch table, prioritized routing rules, and a short execution contract with no concept over-explanation. The only trimmable redundancy is the Examples section re-listing all six subcommands the table already enumerates, which falls short of the 'every token earns its place' anchor.

4 / 5

Actionability

Guidance is fully executable: exact destination skill names per subcommand, concrete path/artifact triggers (~/.claude, session-store.db, MEMORY.md, ~/.pi/agent/sessions), and a verbatim clarification question to ask on ambiguity. As an instruction-only router with copy-paste-ready guidance, no code absence penalty applies.

5 / 5

Workflow Clarity

The decision procedure is complete and unambiguous with explicit priority ordering (explicit agent keyword → path/source heuristics → one short clarification) and a defined fallback for the ambiguous case. It is a simple non-destructive router, so the single-action exception applies and no validation checkpoint is required.

5 / 5

Progressive Disclosure

This is a short (~50 line), self-contained skill with no bundle files and no need for external references; all routing content belongs inline. Its well-organized sections (Subcommands, Routing Rules, Execution Contract, UX Convention) satisfy the simple-skill standard for progressive disclosure.

5 / 5

Total

19

/

20

Passed

Description

78%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 solid router description that clearly states what it does and when to use it, with a well-defined trigger clause. Its main gaps are limited action specificity (routing is the only stated action) and missing the natural keyword variations (agent names, session/chat terms) users would say.

Suggestions

Add one or two more concrete actions to the description, e.g., 'Routes to the matching claude/codex/copilot history-ingest skill based on the source path or agent name the user provides', to raise specificity beyond a single stated action.

Include the natural trigger keywords users would say, such as specific agent names ('claude', 'codex', 'copilot' history) or artifact terms ('session logs', 'chat transcripts'), to improve trigger term coverage.

State the document/history boundary in the description itself (e.g., 'For document or content sources, use wiki-ingest instead') to further reduce overlap risk with the sibling ingest skills.

DimensionReasoningScore

Specificity

The description names its domain ("agent-history ingestion requests") and one concrete action ("Route... to the appropriate specialized history-ingest skill"), matching the anchor for domain plus 1-2 concrete actions but not comprehensive coverage.

3 / 5

Completeness

It explicitly answers both parts: what ("Route generic agent-history ingestion requests to the appropriate specialized history-ingest skill") and when ("Use when the user asks to ingest AI-agent history without directly selecting the underlying agent-specific skill") with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Natural user phrasings like "ingest AI-agent history" and "agent-history ingestion" give good keyword coverage, but common variations users would actually say (e.g., "claude history", "session logs", "chat transcripts") are missing, landing noticeably above anchor 3 rather than at comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (generic history-ingestion requests get routed), but the description operates in the same domain as the six sibling history-ingest skills it dispatches to, creating minor overlap risk with closely related skills rather than minimal conflict risk.

4 / 5

Total

16

/

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

Ar9av/obsidian-wiki

Path

.skills/wiki-history-ingest/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.