Agent skill

Sage Wiki Integrate

by xoai in xoai/sage-wiki

Pipeline skill that wires sage-wiki into an existing project — detects language, installs the client, runs a smoke test, and reports.

MITAuto-check passedTesting & QA

Install Sage Wiki Integrate

skills CLI
$ npx skills add xoai/sage-wiki --skill sage-wiki-integrate -a claude-code

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

GitHub CLI
$ gh skill install xoai/sage-wiki sage-wiki-integrate --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/xoai/sage-wiki.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sage-wiki-integrate .claude/skills/sage-wiki-integrate && 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/

Facts

Skill name
sage-wiki-integrate
GitHub stars
623
Token cost
~861 tokens
SKILL.md length
225 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Pipeline skill that wires sage-wiki into an existing project — detects language, installs the client, runs a smoke test, and reports.

  • Works in 5 steps: Detect language → Choose integration path → Write a smoke test → …
  • Tasks that involve QA and bug reports
  • SKILL.md covers Step 1: Detect language, Step 2: Choose integration path, Step 3: Write a smoke test and Step 4: Run the smoke test, plus 1 more section
  • Calls pip and npm

What it does

Sage Wiki Integrate is an agent skill from xoai/sage-wiki. Pipeline skill that wires sage-wiki into an existing project — detects language, installs the client, runs a smoke test, and reports.

Its SKILL.md is about 860 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 Testing & QA, covering QA and bug reports. It works with Model Context Protocol, Python, TypeScript and npm. The repository describes itself as: sage-wiki is a graph memory and knowledge base that AI agents and humans build and query together. Drop in documents; an LLM compiler turns them into an interlinked wiki with a… The licence is MIT.

When your agent uses it

  • Tasks that involve QA and bug reports

Example prompts

  • “/sage-wiki-integrate”

Requirements

  • Python 3
  • Node.js

Workflow steps

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

  1. Detect language
  2. Choose integration path
  3. Write a smoke test
  4. Run the smoke test
  5. Report

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pip
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pip and npm, which can reach the network depending on how they are called.

    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

Sage Wiki Integrate loads about 861 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 225 words of instructions outside code blocks.

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

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 xoai/sage-wiki at commit d3ef3a1, republished under its MIT licence (© xoai). 225 words, ~861 tokens.

Download SKILL.mdSave it as .claude/skills/sage-wiki-integrate/SKILL.md (or your agent's skills folder).
name
sage-wiki-integrate
description
Pipeline skill that wires sage-wiki into an existing project — detects language, installs the client, runs a smoke test, and reports.
version
0.1.0
generated
skillgen — do not hand-edit

sage-wiki-integrate

Wires sage-wiki into an existing repository so the coding assistant can store and retrieve knowledge with provenance. Test-first — every step is verified before proceeding.

Step 1: Detect language

Check the project root for language markers:

MarkerLanguageIntegration path
pyproject.tomlPythonpip install sagewiki (Python client, P4-3)
package.jsonTypeScript / JavaScriptnpm install sagewiki (TypeScript client, P4-4)
NeitherAnyMCP stdio config

Step 2: Choose integration path

Python (pyproject.toml found)
bash
pip install sagewiki
python
from sagewiki import Client

client = Client(base_url="http://localhost:3333/v1")
# If token-protected:
# client = Client(base_url="http://localhost:3333/v1", token="s3cret")
TypeScript (package.json found)
bash
npm install sagewiki
typescript
import { Client } from "sagewiki";

const client = new Client({ baseUrl: "http://localhost:3333/v1" });
// If token-protected:
// const client = new Client({ baseUrl: "http://localhost:3333/v1", token: "s3cret" });
Neither (MCP stdio)

Add to the project's MCP config:

json
{
  "mcpServers": {
    "sage-wiki": {
      "command": "sage-wiki",
      "args": ["serve", "--transport", "stdio", "--project", "."]
    }
  }
}

Step 3: Write a smoke test

Store a fact, search for it, verify it comes back:

Python smoke test:

python
# Store a fact via capture
resp = client.capture(content="smoke-test: sage-wiki integration works at {now}")
assert resp.status == "ok"

# Search for it
results = client.search(query="smoke-test sage-wiki integration")
assert len(results) > 0, "smoke test failed: no results for stored fact"
print("PASS: smoke test")

TypeScript smoke test:

typescript
const resp = await client.capture({ content: "smoke-test: sage-wiki integration works" });
const results = await client.search({ query: "smoke-test sage-wiki integration" });
console.assert(results.length > 0, "smoke test failed");
console.log("PASS: smoke test");

MCP smoke test (call wiki_capture then wiki_search via your MCP client):

Tool: wiki_capture
Args: { content: "smoke-test: sage-wiki integration works at {timestamp}" }
Expected: confirmation text, no error

Tool: wiki_search
Args: { query: "smoke-test sage-wiki integration" }
Expected: at least one result, no error

Step 4: Run the smoke test

Execute the chosen smoke test. If it fails:

  • Check the server is running (sage-wiki serve --ui)
  • Verify the token is correct (if auth is enabled)
  • Check the server logs for errors

Step 5: Report

After a successful smoke test, confirm:

  • sage-wiki is connected and reachable
  • The chosen integration path works
  • Store → search → verify cycle completes

Then refer to the sage-wiki reference skill for the full tool catalog, error codes, and opt-in features.

Pre-1.0 notice: Every surface here is experimental. Tool semantics, argument names, and REST routes may change between versions. Pin the version you depend on.

Generated by tools/skillgen — reference skill covers 19 tools.

© xoai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/sage-wiki-integrate of xoai/sage-wiki.

Open the folder on GitHubat commit d3ef3a1

Compare with similar skills

Sage Wiki Integrate 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.

Sage Wiki Integrate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sage Wiki Integrate this skillxoai/sage-wiki623—~861Automated safety check: PassMIT
MCP Server BuildershareAI-lab/learn-claude-code78k4 repos~1.2kAutomated safety check: PassMIT
Zizkadb ReleaseZIZKA-AI-SL/ZizkaDB129—~399Automated safety check: PassCustom licence
Agentacct Workflowmikehasa/agentacct766—~1.6kAutomated safety check: PassMIT
Testing Scope MCPdaydreamlive/scope452—~1.2kAutomated safety check: PassCustom licence
Zizkadb TestZIZKA-AI-SL/ZizkaDB129—~358Automated safety check: PassCustom licence

Similar skills

  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 4 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • Zizkadb Release

    ZIZKA-AI-SL/ZizkaDB

    Bumps versions, runs pre-push verification, and publishes ZizkaDB SDK and MCP packages.

    129 GitHub stars~399 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Agentacct Workflow

    mikehasa/agentacct

    A skill your agent uses when working in a repo with agentacct MCP configured, or when asked to track coding-agent work, smoke-test agentacct integrations, or report objective AI-agent task evidence.

    766 GitHub stars~1.6k tokensUpdated 8 days ago
    Testing & QAAuto-check passed
  • Testing Scope MCP

    daydreamlive/scope

    Test Daydream Scope through its stdio MCP server, including disconnected startup, connecttoscope, direct Python stdio client fallback, and lightweight smoke tests.

    452 GitHub stars~1.2k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed
  • Zizkadb Test

    ZIZKA-AI-SL/ZizkaDB

    Run the full ZizkaDB test suite across all layers — lint, Python unit tests, SDK tests, MCP tests, TypeScript tests, and dashboard build verification.

    129 GitHub stars~358 tokensUpdated today
    Testing & QAAuto-check passed
  • Smoke Test

    mastra-ai/mastra

    Create a Mastra project using create-mastra and smoke test the studio in Chrome using Chrome MCP server

    29k GitHub stars~3.3k tokensUpdated today
    Testing & QAAuto-check: notes

More from xoai/sage-wiki

  • Sage Wiki

    xoai/sage-wiki

    Reference skill for sage-wiki — local-first knowledge graph with MCP server, REST API, compiled wiki, and Obsidian-compatible output.

    623 GitHub stars~2.4k tokensUpdated 5 days ago
    Auto-check passed

Questions about Sage Wiki Integrate

What does Sage Wiki Integrate do?

Pipeline skill that wires sage-wiki into an existing project — detects language, installs the client, runs a smoke test, and reports. Sage Wiki Integrate is an agent skill from xoai/sage-wiki. Pipeline skill that wires sage-wiki into an existing project — detects language, installs the client, runs a smoke test, and reports.

When should I use Sage Wiki Integrate?

Sage Wiki Integrate fits situations like: tasks that involve QA and bug reports.

How do I install Sage Wiki Integrate in Claude Code?

Run `npx skills add xoai/sage-wiki --skill sage-wiki-integrate -a claude-code`. Or copy the skill folder (skills/sage-wiki-integrate in xoai/sage-wiki) into .claude/skills/sage-wiki-integrate in your project. Claude Code loads it when a task matches its description.

How do I install Sage Wiki Integrate in Codex?

Run `npx skills add xoai/sage-wiki --skill sage-wiki-integrate -a codex`. Or copy the skill folder (skills/sage-wiki-integrate in xoai/sage-wiki) into .agents/skills/sage-wiki-integrate in your project. Codex loads it when a task matches its description.

Can I use Sage Wiki Integrate 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 xoai/sage-wiki --skill sage-wiki-integrate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sage-wiki-integrate, .gemini/skills/sage-wiki-integrate, .github/skills/sage-wiki-integrate and .opencode/skills/sage-wiki-integrate in your project.

What does Sage Wiki Integrate need to run?

Going by SKILL.md and its folder, Sage Wiki Integrate needs the command-line tools its instructions call (pip and npm). Our summary lists: Python 3; Node.js.

Does Sage Wiki Integrate access the network?

SKILL.md contains no URLs. Its commands use pip and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Sage Wiki Integrate 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 Sage Wiki Integrate use?

Sage Wiki Integrate 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 Sage Wiki Integrate use?

About 861 tokens (SKILL.md is roughly 3.4k 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 Sage Wiki Integrate?

Skills that share tags, products or a category with Sage Wiki Integrate: MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), Zizkadb Release (ZIZKA-AI-SL/ZizkaDB, 129 stars), Agentacct Workflow (mikehasa/agentacct, 766 stars) and Testing Scope MCP (daydreamlive/scope, 452 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sage Wiki Integrate?

xoai (a GitHub user) maintains it in xoai/sage-wiki, which has 623 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 6, 2026.

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