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

oxygen-gtm

Skill2 starsChanged 2 months agoMITView on GitHub

Route a GTM outcome to the correct OXYGEN primitive and select the narrower bundled skill for hosted execution.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the runtime contract.

    line 8
  2. Very specific:

    Search by the actual goal, then hydrate the returned command.

    line 15
  3. Very specific:

    Prefer the kit's existing callables for research/scoring/copy.

    line 32

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

Route the next GTM job

Read the runtime contract. Use this fallback when no narrower OXYGEN skill already fits.

oxygen capabilities search "research and qualify target accounts" --json
oxygen commands get "tables create" --json

Search by the actual goal, then hydrate the returned command. Provider operations have a separate catalog: bounded tools search, then tools get for the selected operation's inputs, readiness, effects and current estimate.

JobNative owner / bundled guide
Company, ICP, offer, rubric, durable learningKnowledge
Choose a repeatable business playRecipes
Working account lists, AI/tool/waterfall columnsTables; kit composition
Canonical company/person/deal truthRecords; inspect promotion and field ownership
Existing-thread replies and direct emailUnibox / Messages
Content, engagement and scheduled postsLinkedIn marketing; Posts, Signals and Publishing
Outreach cadence, enrollment and reply stopsSequences
Deterministic triggers, branches and retriesWorkflows
Adaptive goals and tool choiceAgents; discover the native goal/thread/checkpoint surface
Run failures, provenance and spendDiagnostics

In Tables, use a formula for deterministic transforms, AI for reasoning, a tool column for one provider operation and a native waterfall for ordered fallback. Cross-table links remain Tables relations; they do not automatically create CRM objects. Shared Tags label native objects, and Dashboards summarize their data.

Prefer the kit's existing callables for research/scoring/copy. Inspect one mapped row and its estimate before live work. Long-running production work belongs in durable OXYGEN runs. Return object links, completed scope, cost evidence and held work.

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.