agentleFS
Sign inStart free
timscheueraitimscheuerai/gtm-architecture-template/.agents/skills/oxygen-knowledge/SKILL.md

oxygen-knowledge

Skill2 starsChanged 2 months agoMITView on GitHub

Read and maintain OXYGEN Knowledge pages, sources, revisions and approved context so GTM functions use traceable company knowledge.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    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:

    Read the runtime contract.

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Give the functions durable context

Read the runtime contract. The kit's company/ examples and context/ pages are local authoring inputs. When context is promoted to OXYGEN, record which hosted pages and revisions the motion uses; do not silently maintain competing copies.

oxygen capabilities search "workspace knowledge ICP and offer" --json
oxygen commands get "knowledge index" --json
oxygen commands get "knowledge search" --json

Read the index first, search the concept, then open the relevant pages and their sources. Reuse stable slugs instead of making near-duplicate pages. Follow useful wikilinks/backlinks and cite the slugs/revisions used. Similarity rank is not confidence; inspect semantic availability and lexical fallback when returned.

Sources preserve evidence; pages synthesize it. File durable findings into the closest page with source dates, boundaries and an append-only log entry. Treat model summaries and the demo's synthetic data as such. Use proposals for changes to canonical offer, voice, positioning or pinned playbooks, and follow existing authorized decisions.

Inspect current folder/upsert schemas before creating or moving pages; retain placement unless changing it is intended. Lint structural changes and read back the actual revision and web_url.

A Knowledge sync is a disposable local mirror: sync before editing, push deliberate changes and resolve conflicts. A repository mount is a separate source connection. Discover its current schema and access scope if the user wants to mount their GitHub/Obsidian workspace; cloning this kit does not connect it.

For a scoring/copy run, map the intended evidence/rubric into the callable inputs as described in composition. The presence of a local file or hosted page does not prove that the caller bound its content.

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