Docs
brickbots/PiFinder
Author and edit PiFinder's user-facing documentation in the project's house style.
Build comprehensive open source documentation with contributor guides, architecture docs, README templates, and documentation-as-code workflows Use when the user asks about oss documentation system…
$ npx skills add FerroxLabs/wayland --skill oss-documentation-system -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FerroxLabs/wayland oss-documentation-system --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/software-engineering/oss-documentation-system .claude/skills/oss-documentation-system && rm -rf skills-srcUse ~/.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/
Install the "oss-documentation-system" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/software-engineering/oss-documentation-system into .claude/skills/oss-documentation-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oss-documentation-system", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/software-engineering/oss-documentation-systemType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add FerroxLabs/wayland --skill oss-documentation-system -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FerroxLabs/wayland oss-documentation-system --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/software-engineering/oss-documentation-system .agents/skills/oss-documentation-system && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "oss-documentation-system" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/software-engineering/oss-documentation-system into .agents/skills/oss-documentation-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oss-documentation-system", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FerroxLabs/wayland --skill oss-documentation-system -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FerroxLabs/wayland oss-documentation-system --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/software-engineering/oss-documentation-system .cursor/skills/oss-documentation-system && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "oss-documentation-system" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/software-engineering/oss-documentation-system into .cursor/skills/oss-documentation-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oss-documentation-system", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/FerroxLabs/wayland.git --path src/process/resources/skills-library/bodies/skills/software-engineering/oss-documentation-system--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add FerroxLabs/wayland --skill oss-documentation-system -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FerroxLabs/wayland oss-documentation-system --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/software-engineering/oss-documentation-system .gemini/skills/oss-documentation-system && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "oss-documentation-system" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/software-engineering/oss-documentation-system into .gemini/skills/oss-documentation-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oss-documentation-system", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install FerroxLabs/wayland oss-documentation-systemInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add FerroxLabs/wayland --skill oss-documentation-system -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/software-engineering/oss-documentation-system .github/skills/oss-documentation-system && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "oss-documentation-system" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/software-engineering/oss-documentation-system into .github/skills/oss-documentation-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oss-documentation-system", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FerroxLabs/wayland --skill oss-documentation-system -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install FerroxLabs/wayland oss-documentation-system --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/software-engineering/oss-documentation-system .opencode/skills/oss-documentation-system && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "oss-documentation-system" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/software-engineering/oss-documentation-system into .opencode/skills/oss-documentation-system/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oss-documentation-system", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
oss-documentation-systemBuild comprehensive open source documentation with contributor guides, architecture docs, README templates, and documentation-as-code workflows Use when the user asks about oss documentation system…
Oss Documentation System is an agent skill from FerroxLabs/wayland. Build comprehensive open source documentation with contributor guides, architecture docs, README templates, and documentation-as-code workflows Use when the user asks about oss documentation system, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of oss documentation system or requires a different specialized skill.
Its SKILL.md is about 3.3k 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 Development, covering Technical documentation and Architecture decision records. The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
npmgitFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npm and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Oss Documentation System loads about 3.3k tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 547 words of instructions outside code blocks.
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.
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.
The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 547 words, ~3,348 tokens.
.claude/skills/oss-documentation-system/SKILL.md (or your agent's skills folder).You are an open source documentation architect who helps projects build comprehensive, maintainable documentation systems. You guide through README design, contributor guides, architecture documentation, and documentation-as-code workflows that scale with the project.
Use this skill when:
Do NOT use when:
# Project Name
Brief, compelling one-liner explaining what this project does.
[](link) [](link)
## What is Project Name?
2-3 sentences: what problem does this solve, who is it for, why should they care?
## Features
- **Feature A**: Brief benefit-oriented description
- **Feature B**: Brief benefit-oriented description
## Quick Start
### Installation
```shell
add the package dependency project-nameimport { Project } from 'project-name';
const result = Project.doThing({ input: 'example' });
// Expected output: { status: 'success', data: '...' }We welcome contributions. See CONTRIBUTING.md.
MIT - see LICENSE file for details.
### README Quality Checklist
- [ ] Project name and description clear within 5 seconds
- [ ] Installation takes fewer than 3 steps
- [ ] Working code example is copy-pasteable with expected output
- [ ] All badges are functional and current
- [ ] Links to deeper documentation work
- [ ] License is stated, contributing path is clear
## CONTRIBUTING.md Template
```markdown
# Contributing to [Project]
## Development Setup
### Prerequisites
- Node.js >= 18
- Git
### Local Setup
```shell
git clone [GitHub repository]
cd project
add the package dependency
npm test # Verify setup
npm run dev # Start development modemain: git checkout -b fix/issue-42npm testnpm run lintWe use conventional commits:
feat: new featuresfix: bug fixesdocs: documentation changestest: test additions or fixeschore: maintenance tasksInclude: Steps to reproduce, expected vs actual behavior, environment details, minimal reproduction.
Include: Problem description, proposed solution, alternatives considered, willingness to implement.
## Architecture Documentation
### Architecture Decision Record (ADR) Format
```markdown
# ADR-001: Use PostgreSQL for Primary Data Store
## Status
Accepted (2025-01-15)
## Context
We need a primary data store supporting complex queries with joins,
ACID transactions, JSON document storage, and horizontal read scaling.
## Decision
We will use PostgreSQL as the primary data store.
## Rationale
- Mature, well-tested, widely understood
- jsonb covers flexible schema needs
- Read replicas provide sufficient read scaling
- Team has existing expertise
## Alternatives Considered
- **MongoDB**: Flexible schema but weaker transaction support
- **MySQL**: Widely used but weaker JSON support
## Consequences
- Need connection pooling (pgBouncer) for high concurrency
- Migration tooling must support PostgreSQL dialects
## Review Date
2025-07-15 (6 months after adoption)# Architecture Overview
## System Context
[External Users] → [CDN] → [Web App]
↓
[API Gateway]
/ | \
[Auth] [Core] [Search]
↓ ↓ ↓
[DB] [DB] [Search Index]
## Component Descriptions
- **API Gateway**: Request routing, rate limiting, authentication
- **Core Service**: Business logic and data management
## Data Flow: Request Lifecycle
1. Client sends request to CDN/load balancer
2. Gateway validates authentication token
3. Request routed to appropriate service
4. Service processes request and queries database
5. Response returned through the same path
## Key Design Decisions
| Decision | ADR | Date | Status |
|----------|-----|------|--------|
| Primary database | ADR-001 | 2025-01 | Accepted |
| Authentication | ADR-002 | 2025-01 | Accepted |
| API versioning | ADR-003 | 2025-02 | Accepted |docs/
index.md
getting-started/
installation.md
quick-start.md
configuration.md
guides/
basic-usage.md
advanced-features.md
troubleshooting.md
api/
overview.md
endpoints.md
architecture/
overview.md
adrs/
001-database.md
002-authentication.md
contributing/
setup.md
guidelines.md
releasing.md
mkdocs.yml# GitHub Actions: Build and deploy docs
name: Documentation
on:
push:
branches: [main]
paths: ['docs/**', 'mkdocs.yml']
pull_request:
paths: ['docs/**', 'mkdocs.yml']
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: '3.12'
- run: install the package via pip mkdocs-material
- run: mkdocs build --strict
deploy:
if: github.ref == 'refs/heads/main'
needs: build
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: '3.12'
- run: install the package via pip mkdocs-material
- run: mkdocs gh-deploy --force# .markdownlint.yml
default: true
MD013:
line_length: 120
code_blocks: false
tables: false
MD033: false # Allow inline HTML for badges
MD041: false # First line heading (frontmatter)# Documentation PR check
name: Docs Lint
on: [pull_request]
jobs:
lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: DavidAnson/markdownlint-cli2-action@v16
with:
globs: '**/*.md'
- uses: streetsidesoftware/cspell-action@v6
with:
files: '**/*.md'
- uses: lycheeverse/lychee-action@v1
with:
args: '--no-progress docs/**/*.md README.md' Practical
│
Tutorials │ How-To Guides
(Learning) │ (Problem-solving)
│
Studying ──────────┼──────────── Working
│
Explanation │ Reference
(Understanding)│ (Information)
│
Theoretical| Type | Purpose | Example |
|---|---|---|
| Tutorial | Teach by doing, step-by-step | "Build your first plugin" |
| How-To Guide | Solve a specific problem | "How to configure SSL" |
| Explanation | Provide understanding | "How the cache works" |
| Reference | Describe the machinery precisely | "API endpoint reference" |
1. Start with the user's goal
Bad: "The XConfig class provides configuration management."
Good: "To customize behavior, create a configuration file."
2. Show, then explain - lead with a code example
3. Use consistent terminology - maintain a glossary
4. Test every code example in CI
5. Version your docs to match software versions
6. Progressive disclosure - start simple, add complexity as needed
7. PRs that change behavior must update relevant docs# .github/ISSUE_TEMPLATE/bug_report.yml
name: Bug Report
description: Report a bug or unexpected behavior
labels: ['bug', 'needs-triage']
body:
- type: textarea
id: description
attributes:
label: Bug Description
validations:
required: true
- type: textarea
id: reproduction
attributes:
label: Steps to Reproduce
value: |
1.
2.
3.
validations:
required: true
- type: textarea
id: expected
attributes:
label: Expected Behavior
validations:
required: true
- type: textarea
id: environment
attributes:
label: Environment
value: |
- OS:
- Runtime version:
- Package version:
validations:
required: true# .github/ISSUE_TEMPLATE/feature_request.yml
name: Feature Request
description: Suggest a new feature or enhancement
labels: ['enhancement', 'needs-triage']
body:
- type: textarea
id: problem
attributes:
label: Problem Description
validations:
required: true
- type: textarea
id: solution
attributes:
label: Proposed Solution
validations:
required: true
- type: textarea
id: alternatives
attributes:
label: Alternatives Considered
- type: dropdown
id: willingness
attributes:
label: Would you be willing to submit a PR?
options: ['Yes', 'Yes, with guidance', 'No']### Accuracy
- [ ] All code examples tested against current version
- [ ] API reference matches actual implementation
- [ ] Configuration options are complete and correct
### Completeness
- [ ] All public APIs documented
- [ ] Common use cases have how-to guides
- [ ] Migration guides exist for breaking changes
### Quality
- [ ] No broken links (automated check)
- [ ] No spelling errors (automated check)
- [ ] Consistent formatting and style
### Freshness
- [ ] Getting started guide works for a new user today
- [ ] Deprecated features marked clearly
- [ ] Version-specific docs labeled correctly## Oss Documentation System Analysis
### Assessment
[Key findings and observations]
### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional suggestions]
### Action Items
- [ ] [First action step]
- [ ] [Second action step]
- [ ] [Follow-up task]Input: "Help me with oss documentation system for my current situation"
Output:
Based on your situation, here is a structured approach to oss documentation system:
© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in src/process/resources/skills-library/bodies/skills/software-engineering/oss-documentation-system of FerroxLabs/wayland.
Open the folder on GitHubat commit 4c030c7
Oss Documentation System 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Oss Documentation System this skillFerroxLabs/wayland | 608 | — | ~3.3k | Automated safety check: Pass | Apache-2.0 | |
| Docsbrickbots/PiFinder | 250 | — | ~6.2k | Automated safety check: Pass | GPL-3.0 | |
| Evidence-Backed Documentation Writerbgauryy/octocode | 946 | — | ~2k | Automated safety check: Pass | MIT | |
| Write Vibe ADRmistralai/mistral-vibe | 5.1k | — | ~942 | Automated safety check: Pass | Apache-2.0 | |
| Technical Documentation Templatesbybren-llc/safe-agentic-workflow | 421 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Prosestatic-web-server/static-web-server | 2.4k | — | ~971 | Automated safety check: Pass | Apache-2.0 |
brickbots/PiFinder
Author and edit PiFinder's user-facing documentation in the project's house style.
bgauryy/octocode
Writes, repairs and copyedits project docs against the Google developer documentation style guide, verifying claims in the repository before stating them.
mistralai/mistral-vibe
Creates or updates concise Architecture Decision Records for the Mistral Vibe CLI and registers each one in the AGENTS.md decisions table.
bybren-llc/safe-agentic-workflow
Documentation templates for ADRs, runbooks, architecture docs, and knowledge transfer documents. Use when creating Architecture Decision Records, writing…
static-web-server/static-web-server
Author or edit any prose for the Static Web Server (SWS) project — documentation, design docs, READMEs, PR descriptions, issue bodies, commit message bodies, or other human-readable text — following…
pchalasani/claude-code-tools
Literature-backed English technical-prose writing rules (agent-style, 21 rules).
FerroxLabs/wayland
Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.
FerroxLabs/wayland
OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.
FerroxLabs/wayland
Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.
FerroxLabs/wayland
End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.
FerroxLabs/wayland
Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…
FerroxLabs/wayland
Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…
Categories
Build comprehensive open source documentation with contributor guides, architecture docs, README templates, and documentation-as-code workflows Use when the user asks about oss documentation system…. Oss Documentation System is an agent skill from FerroxLabs/wayland. Build comprehensive open source documentation with contributor guides, architecture docs, README templates, and documentation-as-code workflows Use when the user asks about oss documentation system, related techniques, best practices, or needs guidance in this domain.
Oss Documentation System fits situations like: the user asks about oss documentation system; related techniques; needs guidance in this domain; the request is outside the scope of oss documentation system.
Run `npx skills add FerroxLabs/wayland --skill oss-documentation-system -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/software-engineering/oss-documentation-system in FerroxLabs/wayland) into .claude/skills/oss-documentation-system in your project. Claude Code loads it when a task matches its description.
Run `npx skills add FerroxLabs/wayland --skill oss-documentation-system -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/software-engineering/oss-documentation-system in FerroxLabs/wayland) into .agents/skills/oss-documentation-system in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill oss-documentation-system -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/oss-documentation-system, .gemini/skills/oss-documentation-system, .github/skills/oss-documentation-system and .opencode/skills/oss-documentation-system in your project.
Going by SKILL.md and its folder, Oss Documentation System needs the command-line tools its instructions call (npm and git). Our summary lists: Python 3; Node.js.
SKILL.md contains no URLs. Its commands use npm and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
Oss Documentation System is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Oss Documentation System: Docs (brickbots/PiFinder, 250 stars), Evidence-Backed Documentation Writer (bgauryy/octocode, 946 stars), Write Vibe ADR (mistralai/mistral-vibe, 5.1k stars) and Technical Documentation Templates (bybren-llc/safe-agentic-workflow, 421 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.
Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.