wiki-integrate — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited wiki-integrate (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Connects a new or updated wiki page into the knowledge graph by adding backlinks and an index entry.
Every invocation starts here. Wiki root is the directory containing wiki-config.md. Skills derive it at runtime. Pages this skill writes to follow the structure in wiki-schema.md - both files need to be present.
C:\, D:\, /), OS root, or user home (C:\Users\X, /home/X, /Users/X) → stop immediately. Do not search. Do not attempt to locate wiki-config.md. Go directly to step 6.references/setup-help.md is also available; read it if the user needs orientation or if you get stuck.blacklist, index_excludes, ingested_folder, ingested_subdirs, log_format). If not found, skip to step 6.wiki-config.md, verify wiki-schema.md exists and parses as YAML. Do not proceed to the Workflow below until you have a definite verdict (present / missing / malformed). Then:mandatory_fields, conditional_fields, enums) and proceed to the Workflow.wiki-config is in <available_skills> (from step 3):references/wiki-schema.md.references/setup-help.md for manual repair guidance. If the user explicitly instructs a reset (not as an automatic fallback), warn that it overwrites any customizations, then deploy the default on explicit OK.The same two-branch structure applies if wiki-config.md itself was found malformed in step 4: wiki-config available → stop and recommend /wiki-config, end of turn; unavailable → guided manual repair via setup-help.md.
/wiki-config; offer bundled deployment if unavailable).This skill requires filesystem read and write access. If unavailable, inform the user and stop.
Run wiki-integrate when:
wiki-ingest processes raw source material into wiki pages and links them automatically. wiki-integrate links pages that already exist as wiki content. Do not use one as a substitute for the other.
Wiki-integrate operates on a target page. Provide the path to the newly created or updated page. If no path is provided, ask the user which page to integrate before proceeding.
Config Discovery has already loaded wiki-config.md and wiki-schema.md into context. Do not re-read them; proceed from here assuming both are available.
Read the full content of the target page. Identify the main topic, key concepts, existing [[wikilinks]], and the frontmatter title.
Page_type check: Read the page_type field from the page's frontmatter.
updated:.page_type no longer matches its actual scope (e.g. a knowledge page that has grown into a comparative survey, or a stub that is now substantive), offer a promotion: "This page is typed as `<type>` but reads more like a `<better-type>` now. Want me to update `page_type` while I'm here?" Never auto-promote; wait for explicit confirmation.Confirm the target page is not in a blacklisted path. If it is, stop; wiki skills cannot modify blacklisted paths.
Read index.md. If the target page is not listed, add an entry in the correct section: - [[Page Title]]: One sentence description. \relative/path/to/page.md\``
If already listed, verify the description is still accurate. Update if significantly stale.
From the index catalogue, select 3-8 candidate pages with genuine topic overlap. Connections should be meaningful, not just keyword matches.
Read each candidate in full. Confirm a genuine connection exists: shared concepts, one builds on the other, or a reader would benefit from knowing both. Discard candidates where no real connection exists.
For each confirmed pair, add links in both directions:
[[Candidate Page Title]] where it fits naturally[[Target Page Title]] where it fits naturallyWrite only the new wikilink; do not restructure or rewrite candidate page content. Check each candidate is not blacklisted before writing.
For every page written to (target and each candidate that received a link), also update the updated: frontmatter field to today's date. If a page_type value was inferred and confirmed in Step 1, write it to the target page's frontmatter now. Leave all other frontmatter fields unchanged.
Add the new entry at the top of log.md, below the header line, above all existing entries.
## [YYYY-MM-DD] integrate | <Target Page Title>
Added to index.md. Linked from: [[Page A]], [[Page B]]. Linked to: [[Page C]].Report: whether the target was added to index.md, which pages now link to it, which pages it now links to, and any connections ruled out with brief reasoning.
This skill does wiki work: ingesting, synthesising, organising, and querying .md pages to compound knowledge over time. It does not modify tool or plugin settings, shell out to manipulate application state, or replicate behaviours that belong to whatever app the user reads their notes in. If a request cannot be satisfied by reading and writing .md files inside the wiki root, decline and explain why.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.