{"skill":{"slug":"ubuntu-encyclopedia","displayName":"Ubuntu Encyclopedia","summary":"Ubuntu documentation-first workflow for Ubuntu-specific questions, maintenance, updates, upgrades, package management, system administration, service trouble...","description":"---\nname: ubuntu-encyclopedia\ndescription: >-\n  Ubuntu documentation-first workflow for Ubuntu-specific questions,\n  maintenance, updates, upgrades, package management, system administration,\n  service troubleshooting, networking, storage, logs, release behavior, and\n  diagnostics. Use when the request materially depends on Ubuntu or\n  Ubuntu-specific tooling/behavior such as Ubuntu release behavior,\n  `apt`/`apt-get`/`dpkg`/`snap`, `systemd`/`systemctl`/`journalctl`, Netplan,\n  NetworkManager, package repair, repository/key issues, service failures,\n  boot issues, mounts/`fstab`, permissions, users/groups, or non-trivial\n  Ubuntu maintenance/troubleshooting. Do not use for generic shell, git,\n  Python, Docker, or Linux questions unless Ubuntu-specific semantics matter.\nmetadata: {\"openclaw\":{\"emoji\":\"🟠\",\"homepage\":\"https://manpages.ubuntu.com/manpages/\",\"os\":[\"linux\"]}}\n---\n\n# Ubuntu Encyclopedia\n\n## Overview\n\nUse a docs-first workflow for Ubuntu-specific work. Prefer Ubuntu manpages at `https://manpages.ubuntu.com/manpages/` for command and utility behavior, use official Ubuntu documentation when the task is broader than a manpage, consult cached local copies under `.Ubuntu-Encyclopedia/` before re-fetching, and record useful authoritative excerpts plus environment-specific operational learnings so future work gets faster and safer.\n\nThis skill is for the **Ubuntu distro/admin layer**. It should trigger for Ubuntu-specific package, service, networking, storage, and release-behavior questions — not for generic Linux/shell/dev tooling questions that merely happen to be asked from an Ubuntu machine.\n\n## Workflow\n\n1. **Classify the task**\n   - Decide whether the task is an Ubuntu-specific question, maintenance task, troubleshooting task, command-planning task, upgrade/update task, or live admin task.\n   - Use this skill when the task materially depends on Ubuntu-specific behavior, Ubuntu administration knowledge, Ubuntu package/service behavior, or command semantics that should be verified from manpages or official Ubuntu docs.\n   - Do not use this skill for generic shell work, generic Docker/git/Python work, or generic Linux questions that merely happen to be on Ubuntu when Ubuntu-specific semantics do not matter.\n\n2. **Check local cache first**\n   - Use `.Ubuntu-Encyclopedia/` as the local knowledge/cache root.\n   - Check these locations first when relevant:\n     - `.Ubuntu-Encyclopedia/manpages/manpages.ubuntu.com/...`\n     - `.Ubuntu-Encyclopedia/docs/...`\n     - `.Ubuntu-Encyclopedia/notes/components/...`\n     - `.Ubuntu-Encyclopedia/notes/patterns/...`\n     - `.Ubuntu-Encyclopedia/inventory/...`\n   - If a cached page or note already answers the question well enough, use it.\n\n3. **Consult authoritative Ubuntu sources before answering or acting**\n   - Before answering direct or indirect Ubuntu questions that depend on command syntax, package behavior, service behavior, configuration semantics, or version-sensitive distro details, consult the relevant authoritative source unless the answer is already well-supported by the local cache.\n   - Prefer sources in this order:\n     1. Ubuntu manpages for command and utility behavior\n     2. Official Ubuntu docs for broader workflows and distro-specific guidance\n   - Before performing non-trivial Ubuntu maintenance or troubleshooting work, consult the relevant docs first when:\n     - the exact command semantics matter\n     - service/package behavior is easy to misremember\n     - the action could affect package state, service health, networking, storage, bootability, or access\n   - Do not improvise high-impact Ubuntu admin commands from memory when the docs are easy to check.\n\n4. **Cache consulted docs locally**\n   - When you consult a manpage, save a normalized cache copy under `.Ubuntu-Encyclopedia/manpages/manpages.ubuntu.com/...`.\n   - When you consult broader Ubuntu docs, save a normalized cache copy under `.Ubuntu-Encyclopedia/docs/...`.\n   - Mirror the official path structure as much as practical.\n   - Cache only pages actually consulted; do not try to mirror the whole docs site eagerly.\n   - Use `scripts/cache_manpage.py` or `scripts/cache_doc.py` when appropriate.\n\n5. **Separate authoritative documentation from local observations**\n   - Store manpage-derived material under `.Ubuntu-Encyclopedia/manpages/...`.\n   - Store other official-doc-derived material under `.Ubuntu-Encyclopedia/docs/...`.\n   - Store environment-specific operational knowledge under:\n     - `.Ubuntu-Encyclopedia/notes/components/`\n     - `.Ubuntu-Encyclopedia/notes/patterns/`\n     - `.Ubuntu-Encyclopedia/inventory/`\n   - Distinguish clearly between:\n     - authoritative documentation\n     - observed local configuration/state\n     - inferred best-practice guidance\n\n6. **Record useful local learnings**\n   - After useful live work, save durable notes such as:\n     - package/service management patterns\n     - host-specific quirks\n     - repeated repair/maintenance sequences\n     - networking/storage/admin gotchas\n     - safe/unsafe operational boundaries for the environment\n   - Prefer concise durable notes over re-learning the same Ubuntu-specific details later.\n\n## Live Work Rules\n\n- Treat manpage/docs lookup as the default preflight for non-trivial Ubuntu work.\n- Prefer read/inspect first when entering an Ubuntu area you have not recently reviewed.\n- Treat release upgrades, package repair, service/network/storage changes, and boot-impacting admin work as high-sensitivity areas.\n- When uncertainty remains after checking cache + docs, say so and avoid bluffing.\n- When answering a question, mention when useful whether the answer comes from cached manpages, cached official docs, a fresh lookup, or live observed environment state.\n\n## Data Root\n\nUse this workspace-local root for cache and notes:\n\n- `.Ubuntu-Encyclopedia/`\n\nExpected structure:\n\n- `.Ubuntu-Encyclopedia/manpages/manpages.ubuntu.com/...`\n- `.Ubuntu-Encyclopedia/docs/...`\n- `.Ubuntu-Encyclopedia/notes/components/...`\n- `.Ubuntu-Encyclopedia/notes/patterns/...`\n- `.Ubuntu-Encyclopedia/inventory/...`\n\nUse `scripts/init_workspace.py` to create or repair the expected directory structure.\n\n## Note Destinations\n\n- Component-specific observations → `.Ubuntu-Encyclopedia/notes/components/<component-name>.md`\n- Reusable Ubuntu patterns/gotchas → `.Ubuntu-Encyclopedia/notes/patterns/<topic>.md`\n- Environment-wide deployment/access info → `.Ubuntu-Encyclopedia/inventory/*.md`\n- Cached manpages → `.Ubuntu-Encyclopedia/manpages/manpages.ubuntu.com/...`\n- Cached official docs → `.Ubuntu-Encyclopedia/docs/...`\n\n## Secrets / Sensitive Data\n\n- Do not store plaintext credentials, API keys, session tokens, private URLs, recovery codes, or other secrets in the encyclopedia notes/inventory tree.\n- If a note needs to mention access details, keep it high-level and redact or omit secret material.\n- Treat these workspace notes as operational memory, not as a secrets vault.\n\n## Resources\n\n- `scripts/init_workspace.py` — create or repair the `.Ubuntu-Encyclopedia/` directory tree.\n- `scripts/cache_manpage.py` — fetch and cache a consulted Ubuntu manpage under `.Ubuntu-Encyclopedia/manpages/...`.\n- `scripts/cache_doc.py` — fetch and cache a consulted official Ubuntu docs page under `.Ubuntu-Encyclopedia/docs/...`.\n- `references/workflow.md` — detailed operating workflow and evidence-handling rules.\n- `references/cache-layout.md` — canonical `.Ubuntu-Encyclopedia/` directory structure.\n- `references/topic-map.md` — useful Ubuntu topic groupings for faster authoritative lookup.\n\n## Good Outcomes\n\n- Answer an Ubuntu-specific question using cached or freshly checked manpages/docs instead of guesswork.\n- Inspect a live Ubuntu host after checking the relevant docs and record any new local operational knowledge.\n- Build a growing local Ubuntu knowledge cache that makes later work faster, safer, and more grounded.\n- Turn one-off Ubuntu discoveries into durable notes so future work does not rediscover them from scratch.\n\n## Avoid\n\n- Triggering on generic shell work that is not materially Ubuntu-specific.\n- Answering Ubuntu-specific questions purely from memory when authoritative sources are easy to consult.\n- Treating local observed behavior as if it were guaranteed authoritative documented behavior.\n- Dumping large amounts of low-value docs into the workspace without a reason.\n- Making high-impact live changes before checking the relevant docs when exact behavior matters.\n","tags":{"latest":"1.0.5"},"stats":{"comments":0,"downloads":551,"installsAllTime":21,"installsCurrent":0,"stars":0,"versions":6},"createdAt":1774056334838,"updatedAt":1778492076651},"latestVersion":{"version":"1.0.5","createdAt":1774653729323,"changelog":"Security hardening: restrict cache fetches to approved docs URLs, block traversal/query writes, tighten cache-path handling, and add explicit guidance not to store plaintext secrets in encyclopedia notes.","license":"MIT-0"},"metadata":{"setup":[],"os":["linux"],"systems":null},"owner":{"handle":"kklouzal","userId":"s176y11yv9na3nw5afgpj7d13583g123","displayName":"kklouzal","image":"https://avatars.githubusercontent.com/u/2928845?v=4"},"moderation":null}