agentleFS
timscheueraitimscheuerai/gtm-architecture-template/.agents/skills/oxygen-quickstart/SKILL.md

oxygen-quickstart

Skill2 starsChanged 2 months agoMITView on GitHub

Connect this kit to an OXYGEN workspace, inspect capabilities and complete a small hosted demonstration without paid execution.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are 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.

  • 3

    Very specific

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

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

    Read the runtime contract and function setup.

    line 8
  2. Very specific:

    Read oxygen whoami --json and resolve the intended workspace.

    line 12
  3. Very specific:

    Search oxygen capabilities search "build a small prospect table" --json, then hydrate the chosen command with oxygen commands get "tables …

    line 13

≈ “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

Start with OXYGEN

Read the runtime contract and function setup. Use oxygen unless the operator selected oxygen-dev; keep the selected environment throughout the session.

For this kit, run npm run demo first when the reader needs an example. It requires no account. For a hosted walkthrough:

  1. Read oxygen whoami --json and resolve the intended workspace. If access is not entitled, inspect the returned billing-owner guidance before proposing resources.
  2. Search oxygen capabilities search "build a small prospect table" --json, then hydrate the chosen command with oxygen commands get "tables create" --json.
  3. Inspect existing resources before creating a small Table. Insert only the requested manual/synthetic rows using the returned schema.
  4. Describe the Table, query the bounded rows and return its actual web_url.
  5. Discover a provider operation with oxygen tools search "company research" --json and inspect its schema; discovery does not run it.

For the kit's 13 functions, use npm run setup to preview and npm run setup -- --apply within the requested installation scope. Setup is distinct from paid execution.

For broader onboarding, retrieve the current oxygen-onboarding procedure with oxygen skills get oxygen-onboarding --json; that optional live skill is not bundled here. Use existing company answers rather than restarting an interview.

Return the selected environment, inspected/created objects, relevant next skill and unconfigured dependencies. A first walkthrough does not start a provider run, purchase, send or publishing action.

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.