Skip to content
cccskills
FreePublished on GitHub

wiki-lint

Health-check a persistent markdown wiki. Use this when the user wants to find orphan notes, dangling links, missing pages, graph gaps, contradictions to review, or general wiki maintenance opportunities.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md1.5 KB
  • agents/openai.yaml482 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Wiki Lint

Use this skill for maintenance and health checks.

Start with the vault tool

Run interpreter_vault with action="lint" first. That report is the structural source of truth for:

  • orphan notes
  • isolated notes
  • dangling links
  • repeated missing-page candidates
  • tag coverage summary

You may also use:

  • interpreter_vault with action="search_notes" for follow-up exploration
  • interpreter_vault with action="note_context" for notes that need closer inspection
  • interpreter_vault with action="notes_with_tag" when a tag cluster looks under-maintained

Lint workflow

  1. Run the structural vault lint.
  2. Prioritize the biggest maintenance issues first.
  3. If the user asked for semantic review, inspect the most relevant pages for contradictions or stale synthesis.
  4. Return a prioritized list of findings and next actions.
  5. Do not auto-fix unless the user asked for fixes.

Hard rules

  • Treat the vault lint output as the graph baseline.
  • Be explicit about what is structural fact versus semantic judgment.
  • If you claim a contradiction, cite both sides.
  • If you suspect a stale page but cannot prove it from the files you read, label it as a review candidate rather than a confirmed issue.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Build a period-end accrual schedule by computing each accrual, citing support, and drafting journal entries for controller approval. Use during month-end close; this drafts entries only and must not post them.

The English summary is being prepared. Showing the original description.

openinterpreter/interpreter-workstation28Updated Oct 18, 2026

Audit a spreadsheet for formula accuracy, errors, and common financial-model mistakes. Use for selected ranges, single sheets, or whole-workbook model checks including balance-sheet balance, cash tie-out, roll-forwards, and logic sanity.

The English summary is being prepared. Showing the original description.

openinterpreter/interpreter-workstation28Updated Oct 18, 2026

Use this skill when the user needs advanced Playwright control of an already running browser session through Interpreter's app-managed browser bridge and the `builtin-js-repl` `js_repl` tool, after simple browser page work cannot be handled by the unified `builtin-interpreter` browser page tools.

The English summary is being prepared. Showing the original description.

openinterpreter/interpreter-workstation28Updated Oct 18, 2026

Drive a native desktop app through Interpreter's builtin-cua-driver. Use get_app_state, click/type/scroll/drag, and verify by calling get_app_state again when the user asks to operate a real desktop app, browser chrome, native dialog, menu, secure prompt, file chooser, or hidden/background window.

The English summary is being prepared. Showing the original description.

openinterpreter/interpreter-workstation28Updated Oct 18, 2026

doc

Free

Create, inspect, and edit Word documents (`.docx`) with local code-execution tools. Use for document drafting, structured edits, tables, comments, and layout-sensitive Word deliverables.

The English summary is being prepared. Showing the original description.

openinterpreter/interpreter-workstation28Updated Oct 18, 2026

Design or revise Interpreter UI for non-developers with an ultra-minimal, utilitarian style inspired by the OpenAI website and ChatGPT, not the developer platform. Use when simplifying settings, onboarding, chat, forms, empty states, or helper copy; when removing extra containers, labels, or visual noise; when replacing technical wording with plain language; when clarifying hierarchy and making the main user action obvious; when making every visible label and status understandable to an average HR admin or other non-technical user; when hiding implementation details such as logs, IDs, endpoints, paths, or protocol names; or when a screen must respect the app's existing CSS variables and light/dark theme behavior.

The English summary is being prepared. Showing the original description.

openinterpreter/interpreter-workstation28Updated Oct 18, 2026

See all skills by openinterpreter

Report a problem with this skill