Agent skill

Knowledge Lint

Lint an existing project knowledge base for contradictions, uncited claims, missing connections, stale articles, and orphaned concepts.

MITAuto-check passedDevelopment

Install Knowledge Lint

skills CLI

$ npx skills add flonat/flonat-research --skill knowledge-lint -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research knowledge-lint --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/knowledge-lint .claude/skills/knowledge-lint && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "knowledge-lint" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/knowledge-lint into .claude/skills/knowledge-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "knowledge-lint", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/flonat/flonat-research/tree/main/skills/knowledge-lint

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add flonat/flonat-research --skill knowledge-lint -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research knowledge-lint --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/knowledge-lint .agents/skills/knowledge-lint && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "knowledge-lint" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/knowledge-lint into .agents/skills/knowledge-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "knowledge-lint", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add flonat/flonat-research --skill knowledge-lint -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research knowledge-lint --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/knowledge-lint .cursor/skills/knowledge-lint && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "knowledge-lint" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/knowledge-lint into .cursor/skills/knowledge-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "knowledge-lint", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/flonat/flonat-research.git --path skills/knowledge-lint

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add flonat/flonat-research --skill knowledge-lint -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research knowledge-lint --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/knowledge-lint .gemini/skills/knowledge-lint && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "knowledge-lint" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/knowledge-lint into .gemini/skills/knowledge-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "knowledge-lint", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install flonat/flonat-research knowledge-lint

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add flonat/flonat-research --skill knowledge-lint -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/knowledge-lint .github/skills/knowledge-lint && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "knowledge-lint" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/knowledge-lint into .github/skills/knowledge-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "knowledge-lint", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add flonat/flonat-research --skill knowledge-lint -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install flonat/flonat-research knowledge-lint --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/flonat/flonat-research.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/knowledge-lint .opencode/skills/knowledge-lint && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "knowledge-lint" agent skill from https://github.com/flonat/flonat-research/tree/main/skills/knowledge-lint into .opencode/skills/knowledge-lint/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "knowledge-lint", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: knowledge-lint
GitHub stars: 145
Token cost: ~1.7k tokens
SKILL.md length: 618 words
Files: 1
Skills in repo: 83
Repo updated: Sep 29, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Lint an existing project knowledge base for contradictions, uncited claims, missing connections, stale articles, and orphaned concepts.

Works in 6 steps: Contradictions → Uncited Claims → Missing Connections → …
Checking the integrity of already compiled knowledge before relying on
SKILL.md covers Output Path, When to Use, When NOT to Use and Pre-Check, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Knowledge Lint is an agent skill from flonat/flonat-research. Lint an existing project knowledge base for contradictions, uncited claims, missing connections, stale articles, and orphaned concepts. Use when checking the integrity of already compiled knowledge before relying on or expanding it. Not for compiling raw sources; use $compile-knowledge.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Linting and formatting and Knowledge bases. The repository describes itself as: Shareable Claude Code + Codex infrastructure for PhD researchers — skills, agents, hooks, and rules for academic workflows. The licence is MIT.

When your agent uses it

Checking the integrity of already compiled knowledge before relying on
Tasks that involve Linting and formatting
Tasks that involve Knowledge bases

Example prompts

“/knowledge-lint”

Requirements

Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Agent

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Contradictions
Uncited Claims
Missing Connections
Staleness
Coverage Gaps
Promotion readiness (advisory)

What it can do on your machine

Read from SKILL.md and the folder at commit da27600. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Glob
- Grep
- Write
- Agent
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Knowledge Lint loads about 1.7k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 618 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~76
When it runs · the whole SKILL.md, loaded when a task matches: ~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from flonat/flonat-research at commit da27600, republished under its MIT licence (© flonat). 618 words, ~1,687 tokens.

Download SKILL.mdSave it as .claude/skills/knowledge-lint/SKILL.md (or your agent's skills folder).

name: knowledge-lint
description: Lint an existing project knowledge base for contradictions, uncited claims, missing connections, stale articles, and orphaned concepts. Use when checking the integrity of already compiled knowledge before relying on or expanding it. Not for compiling raw sources; use $compile-knowledge.
allowed-tools: Read, Glob, Grep, Write, Agent
argument-hint: [project-path] or no arguments for CWD
skill-dependencies: compile-knowledge

Knowledge Lint

Substantive consistency checks on the compiled knowledge wiki. Produces correspondence/internal-reviews/KNOWLEDGE-LINT-REPORT.md.

Output Path

Per rules/review-artefact-routing.md (auto-loads in research projects (path-scoped to paper-*/ and paper/)):

Source slug: knowledge-lint
Write reports to: reviews/_project/knowledge-lint/YYYY-MM-DD-HHMM.md inside the project. Path is relative to the research project root, not the Task-Management repo.
Never at project root (./CRITIC-REPORT.md-style filenames are forbidden — pre-rule layout).
Idempotency: if today's file exists, append a same-day descriptor ({date}-revision.md, {date}-r2.md, {date}-pre-submission.md) — never overwrite.
Index update: if reviews/INDEX.md exists, write a one-line entry under "Latest per source" pointing at the new file. Otherwise review-recap will rebuild the index next time it runs.
Infrastructure repos (Task-Management, atlas-workspace, etc.): this section does not apply — the path-scoped rule won't load there.

When to Use

After running compile-knowledge to verify integrity
Before writing a paper section to check the knowledge base is solid
Periodically (monthly) to catch drift
When switching between projects to verify knowledge is current

When NOT to Use

If no knowledge/ directory exists — run compile-knowledge first
For structural project audits — use an installed research-project audit workflow
For bibliography validation — use the configured bibliography validator

Pre-Check

Verify knowledge/ exists and has at least 2 articles (linting a single article is pointless)
If missing: "No knowledge directory found. Run compile-knowledge first."

Checks

1. Contradictions

Scan all articles for claims about the same concept that disagree:

Check	How
Same concept, different claims	Compare Key Findings sections across articles that share wikilinks
Method disagreements	Check if two articles recommend different approaches for the same problem
Factual conflicts	Cross-reference dates, numbers, definitions across articles

Report format:

CONTRADICTION: concept-a.md says "X increases Y" but concept-b.md says "X has no effect on Y"
  Source A: Author (2023) — concept-a.md line 15
  Source B: Author (2024) — concept-b.md line 22
  Resolution needed: check which paper's context applies

2. Uncited Claims

Scan Key Findings sections for assertions without source attribution:

Check	How
Missing citations	Findings that don't reference a paper, session log, or decision
Vague citations	"Some studies show..." without specific references
Self-referential	Citing another knowledge article instead of a primary source

3. Missing Connections

Check for concepts that should link to each other but don't:

Check	How
Shared keywords	Two articles mention the same method/dataset/author but don't cross-reference
Atlas connections	Atlas topic has `connected_topics` that don't have corresponding knowledge articles
Orphaned articles	Articles with zero incoming wikilinks from other articles

Show full SKILL.md (266 more words)Show less

4. Staleness

Check	How
Stale articles	Last updated > 90 days ago AND project has had session activity since
Source drift	New papers in `docs/literature-review/` not compiled into any article
Memory drift	New `[LEARN]` entries in MEMORY.md not reflected in knowledge articles
Session drift	Recent session logs mention findings not in any knowledge article

5. Coverage Gaps

Check	How
Key paper not compiled	Papers cited in `paper-/paper/.tex` but not in any knowledge article
Method not documented	Estimators/methods used in code but not explained in knowledge
Concepts mentioned but not defined	Terms used across multiple articles without a dedicated article

6. Promotion readiness (advisory)

Project knowledge articles are the upstream source that wiki-grow promotes into vault concepts (~/vault/concepts/). Articles that escape their origin project (mentioned in ≥3 corpus docs) get auto-promoted as status: draft and later curated to the concept anatomy (packages/research-atlas-schema/schema.md → "Concept File Schema"): a lead ## In one line definition, encyclopedia-voice body, and a ## In my portfolio section for project-specific prose.

This is advisory, not a hard check — project knowledge lives in the project's own voice and needn't conform. But flagging an article that leads with a crisp, project-agnostic definition as "promotion-ready" (vs. one that opens mid-analysis) helps: the cleaner the lead, the cheaper the eventual draft→curated pass. Note such articles in Recommendations; don't rewrite them here.

Report

Write correspondence/internal-reviews/KNOWLEDGE-LINT-REPORT.md (create directory with mkdir -p if needed):

markdown

# Knowledge Lint Report

**Project:** [name]
**Date:** YYYY-MM-DD
**Articles scanned:** N
**Total words:** ~X

## Summary

| Check | Issues | Severity |
|-------|--------|----------|
| Contradictions | N | High |
| Uncited claims | N | Medium |
| Missing connections | N | Low |
| Staleness | N | Medium |
| Coverage gaps | N | Medium |

## Contradictions (High)

[List each with source references and suggested resolution]

## Uncited Claims (Medium)

[List each with article and line]

## Missing Connections (Low)

[List pairs that should link]

## Staleness (Medium)

[List stale articles with last-updated date and evidence of new activity]

## Coverage Gaps (Medium)

[List uncompiled sources and undocumented concepts]

## Recommendations

1. [Most impactful fix]
2. [Second]
3. [Third]

Cross-References

Skill	Relationship
`compile-knowledge`	Run this first to build/update the wiki
`store-insight`	Use to fix individual gaps found by lint
`research-atlas-coherence`	Complementary — checks topic-level connections, not article-level
`wiki-curate`	Downstream — audits the vault concepts these articles promote into (anatomy, lifecycle, overlap)

Files

Just SKILL.md in skills/knowledge-lint of flonat/flonat-research.

Open the folder on GitHubat commit da27600

Compare with similar skills

Knowledge Lint next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Knowledge Lint compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Knowledge Lint this skillflonat/flonat-research	145	—	~1.7k	Automated safety check: Pass	MIT	8 days ago
Open Knowledgeinkeep/open-knowledge	4.4k	—	~4.7k	Automated safety check: Pass	GPL-3.0	today
Maintain Codex Wikiaiskillstore/marketplace	430	1 repos	~2k	Automated safety check: Notes	None	today
Spec Project Rulesleo-kuang-ai/spec-first	107	—	~1.4k	Automated safety check: Pass	MIT	13 days ago
LLM Wikilewislulu/llm-wiki-skill	655	—	~3.7k	Automated safety check: Pass	None	5 mo ago
Nexus MapperHaaaiawd/Nexus-skills	166	1 repos	~2.5k	Automated safety check: Notes	None	6 mo ago

Similar skills

Open Knowledge
inkeep/open-knowledge
Authoritative agent-runtime contract for working inside an OpenKnowledge project — a markdown-CRDT knowledge base exposed over MCP.
4.4k GitHub stars~4.7k tokensUpdated today
Knowledge ManagementAuto-check passed
Maintain Codex Wiki
aiskillstore/marketplace
Maintain a review-first Markdown knowledge base for Codex practices with source provenance, engineering capture, citation-aware queries, explicit archive and promotion, and deterministic linting.
430 GitHub starsUsed in 1 repo~2k tokens
Knowledge ManagementAuto-check: notes
Spec Project Rules
leo-kuang-ai/spec-first
Use this standalone skill to build or update a project architecture knowledge base (docs/architecture.md) for multi-end monorepos or any repo with a shared layer, from code evidence, or to check…
107 GitHub stars~1.4k tokensUpdated 13 days ago
DevelopmentAuto-check passed
LLM Wiki
lewislulu/llm-wiki-skill
Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers…
655 GitHub stars~3.7k tokensUpdated 5 mo ago
Knowledge ManagementAuto-check passed
Nexus Mapper
Haaaiawd/Nexus-skills
Generate a persistent .nexus-map/ knowledge base that lets any AI session instantly understand a codebase's architecture, systems, dependencies, and change hotspots.
166 GitHub starsUsed in 1 repo~2.5k tokens
DevelopmentAuto-check: notes
Kb
compozy/kb
Operate the kb CLI to build and maintain topic-based Karpathy-style knowledge bases: gated ingestion, decision-model classification, linking, retrieval and review, wiki compilation, lint-and-heal…
110 GitHub stars~4.2k tokensUpdated 12 days ago
Knowledge ManagementAuto-check passed

More from flonat/flonat-research

All 83 skills in this repo

Latex Posters
flonat/flonat-research
Create a large-format academic poster in LaTeX using beamerposter, tikzposter, or baposter.
145 GitHub stars~1.5k tokensUpdated 8 days ago
Auto-check: notes
Skill Creator
flonat/flonat-research
Create, revise, and evaluate reusable AI workflow skills, including trigger-quality tests.
145 GitHub stars~4.4k tokensUpdated 8 days ago
Auto-check passed
DOCX
flonat/flonat-research
Create, read, edit, or convert Microsoft Word documents while preserving professional document structure.
145 GitHub stars~1.2k tokensUpdated 8 days ago
Auto-check passed
PDF
flonat/flonat-research
Read, create, combine, split, rotate, OCR, watermark, secure, or extract content from PDF files.
145 GitHub stars~488 tokensUpdated 8 days ago
Auto-check passed
Init Project Orchestration
flonat/flonat-research
Create or migrate project-level agents, repeatable project workflows, and planning state from one client-neutral contract, then render repository-scoped adapters for both Claude Code and Codex.
145 GitHub stars~1.6k tokensUpdated 8 days ago
Auto-check passed
Pre Commit Audit
flonat/flonat-research
Deliver a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode carriers.
145 GitHub stars~2.8k tokensUpdated 8 days ago
Auto-check: notes

Questions about Knowledge Lint

What does Knowledge Lint do?

Lint an existing project knowledge base for contradictions, uncited claims, missing connections, stale articles, and orphaned concepts. Knowledge Lint is an agent skill from flonat/flonat-research. Lint an existing project knowledge base for contradictions, uncited claims, missing connections, stale articles, and orphaned concepts.

When should I use Knowledge Lint?

Knowledge Lint fits situations like: checking the integrity of already compiled knowledge before relying on; tasks that involve Linting and formatting; tasks that involve Knowledge bases.

How do I install Knowledge Lint in Claude Code?

Run `npx skills add flonat/flonat-research --skill knowledge-lint -a claude-code`. Or copy the skill folder (skills/knowledge-lint in flonat/flonat-research) into .claude/skills/knowledge-lint in your project. Claude Code loads it when a task matches its description.

How do I install Knowledge Lint in Codex?

Run `npx skills add flonat/flonat-research --skill knowledge-lint -a codex`. Or copy the skill folder (skills/knowledge-lint in flonat/flonat-research) into .agents/skills/knowledge-lint in your project. Codex loads it when a task matches its description.

Can I use Knowledge Lint in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add flonat/flonat-research --skill knowledge-lint -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/knowledge-lint, .gemini/skills/knowledge-lint, .github/skills/knowledge-lint and .opencode/skills/knowledge-lint in your project.

What does Knowledge Lint need to run?

SKILL.md names no scripts, command-line tools or credentials: Knowledge Lint is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Agent.

Does Knowledge Lint access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Knowledge Lint safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Knowledge Lint use?

Knowledge Lint is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Knowledge Lint use?

About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Knowledge Lint?

Skills that share tags, products or a category with Knowledge Lint: Open Knowledge (inkeep/open-knowledge, 4.4k stars), Maintain Codex Wiki (aiskillstore/marketplace, 430 stars), Spec Project Rules (leo-kuang-ai/spec-first, 107 stars) and LLM Wiki (lewislulu/llm-wiki-skill, 655 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Knowledge Lint?

flonat (a GitHub user) maintains it in flonat/flonat-research, which has 145 GitHub stars. The repository holds 83 skills in this directory. The repository was last updated on September 29, 2026.

Source: flonat/flonat-research on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Knowledge Lint

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Knowledge Lint

Output Path

When to Use

When NOT to Use

Pre-Check

Checks

1. Contradictions

2. Uncited Claims

3. Missing Connections

4. Staleness

5. Coverage Gaps

6. Promotion readiness (advisory)

Report

Cross-References

Files

Compare with similar skills

Similar skills

More from flonat/flonat-research

Related

Questions about Knowledge Lint