CtrlK
BlogDocsLog inGet started
Tessl Logo

knowledge-base

Build and maintain a company knowledge base as a wiki of interlinked markdown notes in the workspace — a private, compounding Wikipedia. Use when the user wants to start or organize a knowledge base / wiki, ingest sources (URLs, documents, pasted notes) into it, ask questions answered from it, or audit (lint) it. Defines the wiki layout (SCHEMA / index / log / raw / pages), the frontmatter contract, [[wikilink]] conventions, and a deterministic lint script that catches broken links, orphan pages, index drift, and frontmatter problems.

78

Quality

100%

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

100%Weight 40%Scale 1-3

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

The body is a tight, actionable spec: it gives concrete tool calls, a complete frontmatter contract, sequenced workflows with a validate-and-retry lint loop, and correctly pushes the lint engine into a bundled script. It assumes Claude's intelligence and avoids concept over-explanation.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it does not explain what markdown, wikis, or frontmatter are, and every section earns its place with actionable rules. Not score 2: the brief motivating opener ('Unlike a chat that forgets...') is purposeful framing rather than removable padding.

3 / 3

Actionability

Provides copy-paste-ready guidance: concrete tool calls (`file_read wiki/SCHEMA.md`, `web_fetch`, `skill_run({ skill: "knowledge-base", script: "lint", args: { root: "wiki" } })`), a complete frontmatter example, and per-check fix instructions. This matches the score-3 anchor of fully executable, specific examples rather than score-2 pseudocode.

3 / 3

Workflow Clarity

Multi-step processes (Orient → Init → Ingest → Query → Lint) are explicitly numbered, and the lint step includes a validation feedback loop: 'fix every blocking issue... and re-run until clean is true'. This matches the score-3 anchor of clear sequencing with explicit validation and error-recovery loops, not score-2 where checkpoints are implicit.

3 / 3

Progressive Disclosure

SKILL.md serves as a well-sectioned overview while the heavy logic is externalized to a real one-level-deep bundle script (scripts/lint.ts, invoked via skill_run) rather than inlined; no deeply nested references. Matches the score-3 anchor of a clear overview with well-signaled one-level references, verified against the actual bundle structure.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, third-person, and provides explicit 'Use when' triggers covering the full lifecycle (start, ingest, query, audit). It clearly delineates the skill's niche and concrete capabilities without fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Build and maintain a company knowledge base as a wiki', 'ingest sources (URLs, documents, pasted notes)', 'ask questions answered from it', 'audit (lint) it' — plus specific lint checks (broken links, orphan pages, index drift, frontmatter problems). This matches the score-3 anchor of listing multiple specific concrete actions, not the score-2 'some actions' anchor.

3 / 3

Completeness

Explicitly answers both what (build/maintain a wiki, defines layout/frontmatter/wikilink conventions, lint script) and when via a clear 'Use when the user wants to start or organize... ingest sources... ask questions... or audit (lint) it' clause. This is the score-3 anchor of explicit triggers for both dimensions, not score 2 where 'when' is only implied.

3 / 3

Trigger Term Quality

Includes natural phrases a user would say — 'start or organize a knowledge base / wiki', 'ingest sources', 'audit (lint) it' — giving good coverage of common variations. Not score 2 because it goes beyond a single keyword to several user-natural terms.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (a company wiki/knowledge base with a defined file layout and lint tooling) with distinct triggers unlikely to fire for unrelated skills. Not score 2 because the scope and triggers are specific enough to avoid overlap with generic note or memory skills.

3 / 3

Total

12

/

12

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
Open-Curiosity/gini-agent
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.