CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wiki-log

Show recent entries from the LLM Wiki log (wiki/log.md). Uses the standardized

Quality

83%

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.

The body is an exemplary lean, well-organized single-purpose skill: the implementation is a concrete one-liner, sections are compact, and examples show real output. The only gap is that the --op/--since filter implementations are described but not shown, which slightly limits copy-paste actionability.

Suggestions

Show the concrete filter implementations (e.g., `grep "^## \[" wiki/log.md | grep "| ingest " | tail -N` and a date-range variant for --since) instead of describing them as "optional filters".

DimensionReasoningScore

Conciseness

The body is lean and efficient: compact sections (Usage, What it does, Valid ops, Example output, Scripts) with no padding and no explanation of concepts Claude already knows. Every section earns its place — e.g., "No LLM involvement needed — this is essentially: grep + tail" states the whole implementation in one line.

5 / 5

Actionability

The core command `grep "^## \[" wiki/log.md | tail -N` is copy-paste ready and the usage examples are concrete, but the --op and --since filters are only described as "plus optional filters for op type and date range" without a concrete implementation. This is a minor gap that keeps it below fully executable anchor-5 guidance.

4 / 5

Workflow Clarity

This is a simple single-task skill where the single action is unambiguous: run grep + tail on wiki/log.md with optional filters, and the exact one-liner is provided. The read-only operation requires no validation checkpoints, so the simple-skill exception applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external reference files (none exist in the bundle), and is well organized into clear sections. The single outgoing reference (engineering/llm-wiki/skills/llm-wiki/SKILL.md) is clearly signaled and one level deep.

5 / 5

Total

19

/

20

Passed

Description

65%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 clearly states what the skill does and is highly distinctive within its niche, but it lacks an explicit "when to use" trigger clause, which caps completeness. Trigger terms are good though missing a few natural synonyms such as "history" or "activity".

Suggestions

Add a "Use when..." trigger clause (e.g., "Use when the user asks to see recent wiki activity, log history, or what was recently ingested/changed in the wiki") to satisfy completeness.

Include natural synonyms such as "history", "activity", or "changelog" to broaden trigger-term coverage.

Name the filtering actions explicitly (filter by op type or date range) rather than only implying them through the usage syntax.

DimensionReasoningScore

Specificity

"Show recent entries from the LLM Wiki log (wiki/log.md)" names the domain and one concrete action, with filtering only implied through the usage syntax rather than listed as distinct actions. It matches the anchor for naming the domain plus 1-2 concrete actions but not comprehensive coverage.

3 / 5

Completeness

The "what" is clear (show recent entries from the wiki log), but there is no "Use when..." clause or equivalent trigger guidance — the "Usage /wiki-log [--last N]..." line is invocation syntax, not when-to-use guidance. Per the rubric guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like "LLM Wiki log", "wiki/log.md", "recent entries", and op names (ingest, query, lint) give good natural keyword coverage a user would plausibly say. Common synonyms like "history" or "activity" are missing, so it does not reach comprehensive anchor-5 coverage.

4 / 5

Distinctiveness Conflict Risk

"LLM Wiki log (wiki/log.md)" carves out a very specific niche with distinct triggers (wiki log, log entries, op names), with minimal risk of firing for the wrong skill. The description is not generic and would not overlap with unrelated skills.

5 / 5

Total

15

/

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

alirezarezvani/claude-skills

Path

.gemini/skills/wiki-log/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.