Przejdź do treści
Biblioteka skilli
Dokumenty i biuro · Pisanie

agent-docs

/agent-docs

Zakłada, dopasowuje i utrzymuje system dokumentacji dla agentów w istniejącym projekcie: instrukcje, przewodniki i zapisy decyzji.

Licencja
MIT
Ostatnia zmiana repozytorium
10.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
20
Skrypty
2
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 10.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co sprawdzić przed instalacją
  • 2 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: assets/project/.agents/doc-tools/docs.py, scripts/bootstrap.py

Co robi i kiedy

Zakłada, dopasowuje i utrzymuje system dokumentacji dla agentów w istniejącym projekcie: instrukcje, przewodniki i zapisy decyzji.

Oryginalny opis (EN)

Initialize, adapt, review, and maintain an existing project’s agent documentation system, with scoped instructions, source-backed guides, durable decision records, and portable writing workflows. Use for documentation governance or explicit project initialization, not ordinary unrelated code edits.

Jak działa

  1. Choose the requested scope
  2. Same-turn loading is mandatory
  3. Portable materials
  4. Validation and reporting
Sekcje z nagłówków SKILL.md, w oryginale · 37 linii, 617 słów
Podgląd SKILL.md
---
name: agent-docs
description: Initialize, adapt, review, and maintain an existing project’s agent documentation system, with scoped instructions, source-backed guides, durable decision records, and portable writing workflows. Use for documentation governance or explicit project initialization, not ordinary unrelated code edits.
---

# Agent documentation

Establish a project-owned documentation system that another agent can use without this global skill or the upstream repository. Preserve existing instructions, ADR conventions, documentation routes, language, and user edits. Each fact has one owner; active decisions preserve rationale and tradeoffs; frozen history is never current authority.

## Choose the requested scope

- **Design:** read-only inventory and adaptation plan. Do not initialize files.
- **Initialize:** follow [initialization](references/initialize.md), including same-turn instruction loading and semantic acceptance.
- **Maintain:** read the project’s `.agents/docs-config.json`, applicable instructions, and the copied doc-maintenance/prose-standard workflows directly. Update only owners affected by the requested work.
- **Audit:** use those workflows to report evidence-backed findings; fix only when requested. Session-residue probes find candidates, not automatic deletions.
- **Archive:** read the project’s archive-agent-notes workflow and actual decision owners. Retention depends on future decision value, not age, length, or quotas. Respect frozen records.

Use the user’s directory or current project when unambiguous. Discover existing documentation before asking questions. Infer routine layout choices from evidence, and state material assumptions. Authorization to initialize includes scoped reversible integration; do not add a separate approval ceremony for every file. Ambiguous conflicting project policies need a narrow question after independent preparation.

## Same-turn loading is mandatory

Copying a skill does not load it into the current agent. Newly copied skills may be absent from the skill catalog until a later turn. Never rely on discovery refresh, invoke an unavailable skill by name, or postpone quality work to another turn.

For initialization, after copying and before writing project-specific prose, run the project’s `docs.py activate` for **each** of `docs`, `prose`, `trim`, and `archive`, and read all returned content. Run parts separately with sufficient output budgets; if truncated, open every omitted file directly. Apply the instructions to the current work immediately. Root/subtree instructions and sibling references must be read as well. The command records delivery hashes only; it cannot prove comprehension.

Before completion, re-read the generated documents against source evidence and apply the actual prose rules. Record specific applications of fact ownership, complete propositions, session-independent language, and preservation of existing content. A scaffold, a path list, an activation receipt, or a passing structural checker is insufficient. Complete `finish` as described in the initialization reference, and report semantic review and machine checks separately.

## Portable materials

The [project assets](assets/project/.agents/skills/doc-maintenance/SKILL.md) contain adapted documentation maintenance, [prose-standard](assets/project/.agents/skills/prose-standard/SKILL.md), [session-residue review](assets/project/.agents/skills/trim-session-residue/SKILL.md), and [archival](assets/project/.agents/skills/archive-agent-notes/SKILL.md). These are the canonical distributable workflows; copy them intact, then read the project copies. Do not create another paraphrased policy that competes with them.

The bootstrap helper uses Python 3.10+ and the standard library. It only copies policies and integrates entry points; the agent authors actual project content. If that runtime is unavailable, perform the same scoped copying and explicit reads with available file tools, record unrun mechanical checks, and do not claim machine-validated completion. Do not install a runtime without an appropriate task reason.

Package sources and adaptation notes are recorded in [upstream.json](assets/project/.agents/doc-tools/upstream.json); the accompanying [license](LICENSE-DeepSeek) must travel with redistributed material. These are attribution, not runtime dependencies. No upstream checkout, account, network access, or other global skill is required.

## Validation and reporting

Use the copied checker for managed-note structure, local target existence, explicit standing-doc budgets, and archive seals. Existing ADR grammar and semantic accuracy require project checks/review. CI can supply a trusted local Git baseline to detect rewriting both an archive and its manifest. Link fragments, renderer-specific routes, generated-reference freshness, translation semantics, and code examples require applicable project tooling; do not overstate the basic checker.

Report created/adapted owners, preserved conventions, loaded local workflows, operations actually run, and remaining evidence limits. Do not fabricate decision history, alternatives, test results, or successful operation claims. Do not create empty architecture inventories, speculative notes, mandatory translations, or a website pipeline.
Pliki w paczce (20)
  • LICENSE-DeepSeek 1 KB
  • SKILL.md 5 KB
  • agents/openai.yaml 1 KB
  • assets/project/.agents/doc-tools/.gitignore 1 KB
  • assets/project/.agents/doc-tools/LICENSE-DeepSeek 1 KB
  • assets/project/.agents/doc-tools/docs.py 15 KB
  • assets/project/.agents/doc-tools/upstream.json 2 KB
  • assets/project/.agents/skills/archive-agent-notes/SKILL.md 7 KB
  • assets/project/.agents/skills/doc-maintenance/SKILL.md 4 KB
  • assets/project/.agents/skills/doc-maintenance/references/note-policy.md 3 KB
  • assets/project/.agents/skills/doc-maintenance/references/review.md 2 KB
  • assets/project/.agents/skills/doc-maintenance/references/standard.md 4 KB
  • assets/project/.agents/skills/doc-maintenance/references/structure-hierarchy.md 2 KB
  • assets/project/.agents/skills/prose-standard/SKILL.md 9 KB
  • assets/project/.agents/skills/prose-standard/references/examples.md 9 KB
  • assets/project/.agents/skills/trim-session-residue/SKILL.md 7 KB
  • assets/project/.agents/skills/trim-session-residue/references/examples.md 12 KB
  • assets/project/.agents/skills/trim-session-residue/references/recall-batteries.md 5 KB
  • references/initialize.md 8 KB
  • scripts/bootstrap.py 8 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · cyijun/agent-docs-skill100MIT
bbeny123/pragma81MIT

Migawka bazy z 13.11.2026 · wersja paczki 042cbf86168b (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100agent-technical-writer
    Specjalizuje się w dokumentacji technicznej: Architecture Decision Records, dokumentacja API, przewodniki migracji, runbooki i bazy wiedzy.
  • 100flow-docs
    Pisze i sprawdza dokumentację techniczną, README, instrukcje dla agentów, opisy PR, komunikaty commitów i changelogi.
  • 86agent-context
    Pomaga przygotować lub przejrzeć instrukcje dla agentów w projekcie.
  • 100product-documentation
    Buduje i utrzymuje serwisy z dokumentacją użytkownika produktów: tutoriale, przewodniki zadań, opis API i kontrolę przed publikacją.
  • 100notion-knowledge-capture
    Zapisuje rozmowy i notatki jako strony wiki, instrukcje, FAQ lub zapisy decyzji w Notion, czyli trwałą wiedzę.
  • 100user-guide-writing
    Pisze przejrzyste przewodniki i tutoriale dla użytkowników końcowych: dokumenty onboardingowe, instrukcje how-to i strony FAQ z zrzutami ekranu i krokami.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.