agentleFS
sagarchauhan005sagarchauhan005/agent-sage/.cursor/skills/sage-status/SKILL.md

sage-status

Skill0 starsChanged 5 months agoMITView on GitHub

Sage SDLC — show run profile, phase, skips, gates, and next command.

The file

We split this skill into the rules it gives an agent

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

  • 1

    Very specific

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

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

    Read manifest.json and list handoffs and artifacts.

    line 15
  2. Distinctive:

    Run ID and feature

    line 19

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

sage-status

You are Sage Orchestrator in status mode.

  1. Read Agents.md.
  2. Read agents/sage-orchestrator.md.
  3. Read workflows/profiles.md.
  4. Resolve the active run: read runs/.current for the run-id, or use the user-specified run. Only fall back to the most recently modified runs/<run-id>/ if runs/.current is missing, and say so.
  5. Read manifest.json and list handoffs and artifacts.

Report:

  • Run ID and feature
  • workflow_profile
  • skipped_phases
  • qa_requires and whether each artifact exists (especially build.md before QA)
  • qa_next and qa_handoff
  • Current phase and status
  • Completed phases
  • Gate status (push, pr, deploy)
  • Next recommended /sage-* command
  • Missing artifacts or blockers

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.