CtrlK
BlogDocsLog inGet started
Tessl Logo

wiki-ingest

Ingest a source file from raw/ into the LLM Wiki — read, discuss, write summary page, update cross-references across 5-15 pages, regenerate index, append to log. Usage /wiki-ingest <path-to-source>

61

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/wiki-ingest/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, concise, and actionable with concrete script paths and a clear multi-step workflow, held back only by minor flow/list redundancy and the lack of an explicit validation feedback loop.

Suggestions

Consolidate the prose 'flow' summary and the 'What happens' numbered list to remove the restated sequence.

Add an explicit validation/verification step in the workflow (e.g., after writing, verify touched pages resolve and index is consistent before reporting).

Co-locate or summarize the ingest-workflow reference so skill-level navigation does not depend on a file outside the bundle.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence without explaining wiki concepts, but the flow paragraph and the 'What happens' list restate the same sequence, a minor redundancy that could be trimmed.

4 / 5

Actionability

It gives concrete, executable commands with full script paths and flags (e.g., 'append_log.py --op ingest --title "<title>"'), with only minor gaps in showing ingest_source.py's argument syntax.

4 / 5

Workflow Clarity

An eight-step sequence with a Confirm checkpoint, contradiction flagging, and a final Report step gives clear sequencing; it lacks an explicit validate-and-retry feedback loop, but the confirm/report checkpoints keep it above 3.

4 / 5

Progressive Disclosure

Sections are well-organized with a clearly signaled, one-level-deep Skill Reference block pointing to ingest-workflow.md and SKILL.md; the detailed workflow reference lives outside the skill bundle, a minor navigation gap.

4 / 5

Total

16

/

20

Passed

Description

67%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 specific and clearly distinct, with a strong concrete action list, but it omits an explicit "when to use" trigger clause and relies on a single phrasing of trigger terms.

Suggestions

Add an explicit 'Use when...' clause stating when to invoke this skill (e.g., 'Use when adding a new source to the LLM Wiki or when the user asks to ingest a paper, article, or note into raw/').

Broaden trigger terms with natural synonyms a user might say, such as 'add to wiki', 'summarize source', or 'index a new source'.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "read, discuss, write summary page, update cross-references across 5-15 pages, regenerate index, append to log" — giving comprehensive coverage of the ingest workflow.

5 / 5

Completeness

The "what" is clearly and fully stated, but there is no explicit "Use when..." trigger clause — only a usage-syntax line — so per the missing-trigger cap it stays at 3.

3 / 5

Trigger Term Quality

It surfaces relevant domain keywords ("ingest", "LLM Wiki", "source file", "raw/") but offers a single phrasing with no synonyms or common variations a user might naturally say.

3 / 5

Distinctiveness Conflict Risk

"Ingest a source file from raw/ into the LLM Wiki" carves out a clear, narrow niche with a distinct trigger and minimal overlap risk with other skills.

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/claude-skills
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.