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

oxygen-table-tidy

Skill2 starsChanged 2 months agoMITView on GitHub

Inspect and improve OXYGEN Table structure, visibility and formatting while preserving raw data, dependencies and record identity.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    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

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

Make the Table usable

Read the runtime contract. Use oxygen-dedupe for identity matching; this skill handles columns and presentation.

Discover oxygen commands get "tables tidy-suggest" --json and run the suggestion pass read-only on the named Table. Inspect its actual schema, dependencies and a bounded sample.

Group findings by overlapping columns, order, types, formatting, visibility and suspicious values. Similar names do not prove identical semantics. Record the consumers of a proposed change before applying it.

Separate workspace hiddenByDefault curation from the user's empty-column collapse. Hidden columns still exist and may feed downstream formulas or AI inputs; hidden is not archived. Prefer a visibility change when the goal is a cleaner view, and keep raw evidence when adding a cleaned/derived value.

A completely blank enrichment column may never have run for older rows. Inspect run/provenance and current backfill preview instead of immediately forcing every row to rerun. Paid backfill requires the selected row scope and current cap.

Apply requested reversible formatting/order/visibility fixes within scope. Present data-changing retypes, archival or paid cleanup concretely before any additional authorization needed. Do not merge records or overwrite raw values as a cosmetic tidy operation.

Re-describe the Table and inspect representative rows after changes. Return what changed, affected dependencies, held suggestions and the Table link.

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.