Nixos Local logo

Nixos Local

Community
Firstp1ck
nixos-local

Use automatically for NixOS, Nix, nixpkgs, flakes, Nix language, Home Manager-adjacent Nix configuration, nix commands, NixOS modules/options, packages, overlays, derivations, and troubleshooting. Prefer local official NixOS/Nix documentation evidence via nixoswiki tools before web sources.

Overview

PublisherFirstp1ck
Repositorypi-coding-agent-forge
Skill namenixos-local
Stars
93
Forks
22
Bundled files
5
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 5 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Firstp1ck on GitHub. Read the source before you install it.

Installation

Install the Nixos Local AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Firstp1ck/pi-coding-agent-forge/tree/main/pi-extension-nixos-wiki-local/skills/nixos-local
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Firstp1ck/pi-coding-agent-forge.git /tmp/pi-coding-agent-forge
mkdir -p .claude/skills
cp -r /tmp/pi-coding-agent-forge/pi-extension-nixos-wiki-local/skills/nixos-local .claude/skills/nixos-local
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Nixos Local in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Nixos Local on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Nixos Local is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

NixOS/Nix Local Wiki

Use the local official NixOS/Nix documentation corpus before web sources.

Setup requirement

This skill requires the local documentation corpus at:

txt
~/.nixoswiki

If the corpus is missing or empty, tell the user to run:

txt
/nixoswiki-local-setup

The setup command is designed to be idempotent and minimal: shallow, sparse, blob-filtered Git checkouts with common images/binaries excluded.

After package/corpus changes, verify local behavior with /nixoswiki-smoke-test or nixoswiki_smoke_test({ maxSearchResults: 5 }).

Required workflow

  1. Classify the question: Nix command, flake workflow, Nix language, NixOS module/option, nixpkgs packaging/overlay, or store/cache/daemon/profile issue.
  2. Start with nixoswiki_search({ query, limit: 5, includeSnippets: false }) for NixOS/Nix issues.
  3. Use nixoswiki_sections({ page, maxSections: 40-80 }) when the right page is found but the relevant heading is unclear.
  4. Prefer exact nixoswiki_extract({ page, section, maxChars: 4000-8000, maxSections: 2-5 }) for final citations.
  5. Use query extraction only for exploration, then switch to exact section names when possible.
  6. Use nixoswiki_read only when broad page context is needed.
  7. Use nixoswiki_related when the issue spans linked topics.
  8. Run read-only local diagnostics when system/project evidence is relevant.
  9. Compare documentation guidance with observed local state.
  10. Cite local paths and section names in final answers.
  11. Ask before destructive or user-facing changes.

Source priority

  1. Local official NixOS/Nix corpus via nixoswiki_* tools.
  2. Local project/system evidence relevant to the user's current environment.
  3. Official online NixOS/Nix documentation only when local docs are missing, stale, or insufficient.
  4. Other sources only when necessary and clearly labeled.

Local source selection

Use references/source-map.md when choosing which official corpus to trust first:

  • ~/.nixoswiki/nix/ for Nix CLI, Nix language, store, daemon, and nix.conf behavior.
  • ~/.nixoswiki/nixpkgs/ for NixOS modules/options and nixpkgs packaging/overlays/stdenv.
  • ~/.nixoswiki/nix.dev/ for tutorials, learning paths, and practical examples.

For flakes, combine NixOS/nix command semantics with NixOS/nix.dev practical workflow guidance when available. For generated NixOS option pages that are absent from the sparse corpus, use the closest manual section locally and check official online docs if exact option semantics are needed.

Read-only diagnostics examples

Use these only when relevant and available on the current system:

bash
nix --version
nix flake metadata --no-write-lock-file .
nix flake check --no-build .
nix eval --raw nixpkgs#hello.name
rg "services\.|environment\.systemPackages|programs\." .

Do not assume the user is on NixOS. If nix is absent, rely on local docs and project files instead of attempting package installation. Load references/non-nixos-host-policy.md when host assumptions matter.

Avoid mutation without explicit approval:

bash
nixos-rebuild switch
nix profile install
nix-env -iA
rm -rf /nix/store

Token/output discipline

  • Prefer search -> sections -> exact section extract for final answers.
  • Keep search limits small (limit: 5-10) and snippets off unless needed.
  • Use maxSections around 2-5 and maxChars around 4000-8000 for focused extracts.
  • If omittedSectionCount or truncated: true affects confidence, say so explicitly.
  • If the sparse corpus lacks generated command/option reference pages, say that confidence is lower and verify with official online docs when necessary.

Tool usage

  • nixoswiki_search({ query, limit, includeSnippets }): find candidate pages; snippets default off.
  • nixoswiki_sections({ page, maxSections }): inspect headings before extracting from large pages.
  • nixoswiki_extract({ page, section, maxChars, maxSections }): retrieve focused exact sections; best for final answers.
  • nixoswiki_extract({ page, query, maxChars, maxSections }): retrieve query-relevant sections; best for exploration.
  • nixoswiki_read({ page, maxChars }): retrieve broad page text; use sparingly.
  • nixoswiki_related({ page, limit }): discover linked local pages.
  • nixoswiki_smoke_test({ maxSearchResults }): verify parser/search/extract/read behavior after package or corpus updates.

Citation format

Use local source citations like:

txt
Sources:
- ~/.nixoswiki/nixpkgs/nixos/doc/manual/configuration/configuration.md — Relevant section
- ~/.nixoswiki/nix.dev/source/tutorials/first-steps/index.md — Relevant section

See references:

  • references/troubleshooting-policy.md
  • references/safety-rules.md
  • references/query-expansions.md
  • references/source-map.md
  • references/non-nixos-host-policy.md

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Nixos Local AI skill do?

Use automatically for NixOS, Nix, nixpkgs, flakes, Nix language, Home Manager-adjacent Nix configuration, nix commands, NixOS modules/options, packages, overlays, derivations, and troubleshooting. Prefer local official NixOS/Nix documentation evidence via nixoswiki tools before web sources.

Why use Nixos Local on TypingMind?

Because you install it once and use it with any model. Nixos Local is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Nixos Local in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Firstp1ck/pi-coding-agent-forge/tree/main/pi-extension-nixos-wiki-local/skills/nixos-local. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Nixos Local?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Nixos Local?

As many as you like. As long as a model supports skills, you can use Nixos Local with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Nixos Local AI skill free?

Yes. It is published on GitHub by Firstp1ck under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇