agentleFS
Sign inStart free
LangChainKnown publisherlangchain-ai/docs/docs-release-watch/skills/openwiki/SKILL.md

openwiki

Skill445 starsChanged 10 days agoMITView on GitHub

Analyze OpenWiki releases against LangChain OpenWiki docs and prepare one-feature documentation updates.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 1 is distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the product is OpenWiki.

    line 8
  2. Very specific:

    When unsure, open a small clarifying ticket/PR only if a reader of the current docs would be misled.

    line 35
  3. Very specific:

    After research returns features with needs_docs: true, read /memories/agent/openwiki-releases.md and skip any already recorded for that tag.

    line 41
  4. Very specific:

    Call get_docs_file on AGENTS.md and read it in full.

    line 42
  5. Very specific:

    If a new page is required, also plan the src/docs.json navigation update.

    line 45
  6. Very specific:

    After shipping, append the release tag, feature name, Linear URL, and PR URL to /memories/agent/openwiki-releases.md.

    line 47
  7. Very specific:

    Keep /memories/agent/AGENTS.md short: last processed OpenWiki tag and date only.

    line 48
  8. Very specific:

    Use cold memory file /memories/agent/openwiki-releases.md:

    line 52

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OpenWiki docs release skill

Use this skill when the product is OpenWiki.

Sources of truth

  • Releases: https://github.com/langchain-ai/openwiki/releases via get_eligible_release / get_release_notes
  • Docs paths in langchain-ai/docs:
    • src/oss/openwiki/ (all OpenWiki pages)
    • Navigation entries for OpenWiki in src/docs.json
    • Docs style authority: root AGENTS.md in langchain-ai/docs (read via get_docs_file before drafting)
  • Changelog page in docs: src/oss/openwiki/changelog.mdx (points at GitHub releases)

What usually needs docs

Prioritize user-facing changes:

  • New CLI commands, flags, or subcommands
  • New coding-agent integrations or providers
  • New modes, workflows, or config surfaces
  • Behavior changes that make existing docs wrong
  • New requirements (Node version, auth, permissions)

Usually skip docs for:

  • Internal refactors with no user-visible change
  • Dependency bumps with no behavior change
  • Pure bug fixes that do not change documented behavior

When unsure, open a small clarifying ticket/PR only if a reader of the current docs would be misled.

Workflow for one OpenWiki release

The main agent must run phase 1 through the release-research subagent first (diff + source investigation). This skill guides phase 2 shipping and judgment details the subagent also uses.

  1. After research returns features with needs_docs: true, read /memories/agent/openwiki-releases.md and skip any already recorded for that tag.
  2. Call get_docs_file on AGENTS.md and read it in full. Then call get_docs_file for OpenWiki pages named in the research report.
  3. For each remaining feature:
    • Edit surgically from the page get_docs_file content, following the docs repo AGENTS.md.
    • If a new page is required, also plan the src/docs.json navigation update.
    • Load the ship-docs-update skill and ship that feature alone with the research report's evidence as evidence_json.
  4. After shipping, append the release tag, feature name, Linear URL, and PR URL to /memories/agent/openwiki-releases.md.
  5. Keep /memories/agent/AGENTS.md short: last processed OpenWiki tag and date only.

Memory format

Use cold memory file /memories/agent/openwiki-releases.md:

# OpenWiki release tracking

## v0.7.0
- feature: GitHub Copilot CLI integration
  - linear: https://linear.app/...
  - pr: https://github.com/langchain-ai/docs/pull/...
- feature: entra auth configuration
  - linear: https://linear.app/...
  - pr: https://github.com/langchain-ai/docs/pull/...

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free