agentleFS
skillsaasskillsaas/microsoft-excel/AGENTS.md

microsoft-excel

AGENTS.md0 starsChanged 30 days agoMITView on GitHub

This repository is an Agent Skill for Microsoft Excel (npm microsoft-excel, GitHub skillsaas/microsoft-excel).

The file

Files
AGENTS.md

AGENTS.md

This repository is an Agent Skill for Microsoft Excel (npm microsoft-excel, GitHub skillsaas/microsoft-excel).

  • Entry point: SKILL.md. Load it when a task involves Excel workbooks, formulas, .xlsx, .xlsm, .xlsb, .xls or .csv files.
  • Load files in references/ only when SKILL.md points to them.
  • Scripts in scripts/ (call them by absolute path, python <skill-dir>/scripts/NAME.py) are read-only or write only to new paths. Run python tests/smoke_test.py after changing them. Never pass recalc.py --sandboxed yourself; only a human or operator who set up a no-network sandbox may.
  • Contributing: keep SKILL.md under 500 lines, test every code block, cite official docs, and do not use em dashes.

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.