CtrlK
BlogDocsLog inGet started
Tessl Logo

wiki-ingest

Ingest a raw source document into the wiki. Reads the source, extracts key information, creates or updates wiki pages, maintains cross-references, and logs the operation. Use when the user adds a new source or says 'ingest this'.

76

Quality

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise, well-structured, and actionable with concrete paths and an end-to-end worked example. Its main gap is the absence of a verification step for a batch operation that mutates many wiki pages and appends to a shared log. Adding an explicit validation checkpoint would lift the workflow-clarity score.

Suggestions

Add a verification step before the log entry — e.g., confirm all new [[wikilinks]] resolve to existing pages and that index.md entries point to real files — so the batch operation has an explicit feedback loop.

Show a concrete frontmatter example (with real updated/source_count values) instead of only naming the fields, so the create-or-update step is fully copy-paste ready.

Replace the log placeholders ([list], [1-2 sentences]) with a filled-in example drawn from the quantum-computing walkthrough for a more actionable reference.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it gives task-relevant bullet lists and concrete paths without explaining what a wiki or entity is, matching the score-3 'lean and efficient' anchor.

3 / 3

Actionability

Provides concrete file paths and exact frontmatter fields ('read memory/wiki/index.md', 'update updated date and source_count', 'Create memory/wiki/sources/<source-name>.md'), giving specific actionable guidance for an instruction-only skill where code absence is not penalized.

3 / 3

Workflow Clarity

Steps are clearly sequenced (Step 1-5 with sub-steps), but this is a batch operation touching 5-15 pages and a log, and there is no validation/verification checkpoint (e.g., confirming cross-references resolve or pages are well-formed), which caps the score at 2 per the rubric's feedback-loop note.

2 / 3

Progressive Disclosure

A self-contained, single-purpose skill with well-organized sections (Workflow > Step N > Example) and no nested external references, satisfying the simple-skills note that well-organized sections alone can earn a 3.

3 / 3

Total

11

/

12

Passed

Description

100%

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 concise, specific, and complete: it states the concrete actions the skill performs and gives an explicit natural-language trigger. It is third-person and free of fluff or over-claims. It is among the strongest examples in the reference set.

DimensionReasoningScore

Specificity

Enumerates multiple concrete actions ('extracts key information, creates or updates wiki pages, maintains cross-references, and logs the operation'), matching the score-3 anchor that lists several specific verbs rather than naming only a domain.

3 / 3

Completeness

Explicitly answers both what (the four ingestion actions) and when ('Use when the user adds a new source or says "ingest this"'), matching the score-3 anchor with an explicit 'Use when' clause.

3 / 3

Trigger Term Quality

Includes natural user phrasings — 'Use when the user adds a new source or says "ingest this"' — that a user would actually say, giving strong trigger coverage rather than jargon.

3 / 3

Distinctiveness Conflict Risk

The wiki-ingestion niche with the 'adds a new source'/'ingest this' trigger is clearly distinct and unlikely to fire for unrelated skills, matching the score-3 'clear niche' anchor.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
open-gitagent/opengap
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.