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

oxygen-recipes

Skill2 starsChanged 2 months agoMITView on GitHub

Find and inspect a versioned OXYGEN business play, preflight its resources and adapt it to the reader's GTM goal.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the user's goal and first-batch guide.

    line 8
  2. Distinctive:

    Use the selected play's actual dependency order and current command schemas.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Choose a useful play

Read the user's goal and first-batch guide. A Recipe is an advisory playbook whose steps use native Tables, Workflows, Sequences and other primitives.

oxygen capabilities search "proven play for warm LinkedIn engagement" --json
oxygen commands get "recipes list" --json
oxygen commands get "recipes show" --json

List a bounded set by goal or lifecycle stage, read one selected Recipe and explain its prerequisites, input, output and limits. Use the reader's actual context; do not make a network motion the default for someone who has no relevant network or chose a different channel.

For a first LinkedIn motion, inspect the current linkedin-network-first-motion recipe if available. Distinguish captured events from coverage of the existing network, and make any standing auto-enrollment grant explicit.

If the Recipe includes a staged kit or Blueprint, inspect the current apply/preflight command. Preview the resources and cumulative forecast before installation. Reuse existing matching stages and record installed versions. Read the resulting resource states; installation does not authorize enabling, enrollment, sending or paid steps.

Use the selected play's actual dependency order and current command schemas. For this repo's functions, prefer the existing installer over creating duplicate equivalents.

Return the chosen play, rationale, prerequisites, installed objects if requested, and the next useful action. A recommended or installed Recipe is not a completed motion.

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.