agentleFS
Sign inStart free
ZeeshanSultanZeeshanSultan/DocGov/skills/publish/SKILL.md

publish

Skill0 starsChanged 2 months agoMITView on GitHub

Analyze which documentation is safe to publish externally, detect information that would leak, and produce external-lens rewrite briefs. Use before publishing docs, opening a repository, or moving internal documentation to a public site.

60 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use render, ingest and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • suxrobGMSkill

    render

    Generate raster images (PNG, JPEG, WebP) from natural language prompts using Python rendering engines. Covers graphics, charts, layouts, and procedural art. Not for SVG output.

    Also in 3 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 6 projects that use this

  • genomewalkerSkill

    explore

    RLM-style recursive memory exploration - dynamically navigate the memory graph

    Also in 4 projects that use this

  • GoogleSkill

    translate

    Translates a common phrase into one or more languages.

    Also in 3 projects that use this

  • aakash-dharSkill

    optimize

    Analyzes code for performance issues including slow algorithms, memory leaks, unnecessary re-renders, database query problems, and resource bottlenecks. Use when the user says "this is slow", "optimize this", "performance issue", "why is this taking so long?", or "make this faster".

    Also in 3 projects that use this

  • AnthropicSkill

    analyze

    Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 49 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    rewrite[] — write a new document, do not edit the old one: Use the brief in briefs[].

    line 26
  2. Distinctive:

    no internal jargon, team names, ticket ids, or hostnames

    line 28
  3. Distinctive:

    no unmitigated risks, no infrastructure topology

    line 29
  4. Distinctive:

    every example runnable exactly as written

    line 32

“Common” is measured: kept by at least 6 in 10 of the 49 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

Publishing analysis

!docgov publish --json --compact $ARGUMENTS 2>&1 | head -c 10000

The rule this skill exists to enforce

An external document is a different artifact, not a copy of an internal one. They serve different readers and answer different questions. Copying internal documentation outward — even with the secrets removed — produces documentation that is technically safe and practically useless, and it leaks information structure even when it leaks no values.

What to do

  1. blocked[] — report and stop. These contain detected sensitive patterns. List the file, line and what was found. Do not publish, do not "clean up and publish anyway" on your own judgement. Hand it back to the user.
  2. rewrite[] — write a new document, do not edit the old one. Use the brief in briefs[]. Under the external lens:
    • no internal jargon, team names, ticket ids, or hostnames
    • no unmitigated risks, no infrastructure topology
    • task-oriented: what the reader wants to do, not how the system is built
    • prerequisites stated explicitly, because the external reader has none of your context
    • every example runnable exactly as written
  3. publishable[] — still read before shipping. Soft flags (ticket references, email addresses, work-in-progress markers) are judgement calls, not false positives.
  4. Never publish. This skill analyzes and drafts. A human approves and a human ships. Say that explicitly when you report, and do not offer to push anything.

The threat model / public security model pair

These are the canonical example of the same subject needing two documents. The threat model is visibility: internal and names unmitigated risks. The public security model is visibility: public and says what you protect and how to report a vulnerability. One is not a redaction of the other.

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