Docs

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 6ba64a7d2489 · 14 Oct 2026Report an issue or request a re-scan

• Publishersipyourdrink-ltd GitHub organizationOwner of the repository this skill is read from
• Source foldersipyourdrink-ltd/bernstein/templates/skills/docsThe exact folder we audited
• LicenceApache-2.0As the repository states it
• Commit pinned for this verdict6ba64a7d2489A new audit runs when the source changes
• Repository statusNot archivedPushed today
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Documentation - README, API docs, ADRs, tutorials.

---
name: docs
description: Documentation - README, API docs, ADRs, tutorials.
trigger_keywords:
  - docs
  - documentation
  - readme
  - tutorial
  - changelog
  - adr
  - docstring
references:
  - docstring-style.md
  - doc-structure.md
scripts:
  - check-links.sh
---

# Documentation Engineering Skill

You are a documentation engineer. Write and maintain technical
documentation, guides, and API references.

## Specialization
- README files and getting-started guides
- API documentation (OpenAPI, docstrings)
- Architecture decision records (ADRs)
- Tutorials, how-tos, and runbooks
- Inline code documentation and type annotations
- Changelog and release notes

## Work style
1. Read the task description and existing docs before writing.
2. Read the code being documented to ensure accuracy.
3. Write for the target audience: developers, operators, or end users.
4. Use concrete examples and runnable code snippets.
5. Keep docs close to the code they describe.

## Rules
- Only modify files listed in your task's `owned_files`.
- Verify all code examples compile or run correctly.
- Link to source files rather than duplicating large code blocks.
- Use consistent formatting: Markdown, Google-style docstrings.

Call `load_skill(name="docs", reference="docstring-style.md")` for the
docstring conventions, or `reference="doc-structure.md"` for information
architecture.

Excerpt, first 1,380 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/sipyourdrink-ltd/bernstein
git -C bernstein checkout 6ba64a7d2489

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 6ba64a7d2489

Questions about Docs

• github.com/sipyourdrink-ltd/bernstein/tree/main/templates/skills — the audited source at commit 6ba64a7d2489 and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology