agentleFS
razvan-scrazvan-sc/claude-atlas/.claude/skills/atlas-status/SKILL.md

atlas-status

Skill0 starsChanged 4 months agoMITView on GitHub

View the latest status, risks, and highlights for an Atlas project

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. AvinashP/AgentsAtlas★ 7same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

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

    Use the atlas MCP server. All tool calls use the mcp__atlas__ prefix.

    line 13
  2. Very specific:

    Check if a project key was provided as an argument (e.g., /atlas-status SAFET-2318).

    line 17
  3. Very specific:

    If a project key (not ARI ID) was provided, first call mcp__atlas__list_projects with limit: 50 to find the matching project's ARI ID.

    line 18
  4. Distinctive:

    If not provided, ask the user: "Which project would you like to check?

    line 19
  5. Very specific:

    Call mcp__atlas__get_project_updates with the project's ARI ID.

    line 21
  6. Very specific:

    Use these indicators: on_track = ON_TRACK, at_risk = AT_RISK, off_track = OFF_TRACK, done = DONE

    line 33
  7. Distinctive:

    If there are more updates beyond the first, add: "_N more status updates available._"

    line 36
  8. Distinctive:

    If no highlights, omit this section.

    line 45
  9. Very specific:

    Update summaries are in Atlassian Document Format (ADF) JSON.

    line 51

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

Atlas Project Status

Show the latest status update, risks, and highlights for a specific Atlas project.

MCP Server

Use the atlas MCP server. All tool calls use the mcp__atlas__ prefix.

Workflow

  1. Check if a project key was provided as an argument (e.g., /atlas-status SAFET-2318).
    • If a project key (not ARI ID) was provided, first call mcp__atlas__list_projects with limit: 50 to find the matching project's ARI ID.
    • If not provided, ask the user: "Which project would you like to check? Please provide the project key (e.g. SAFET-1234)."
  2. Call mcp__atlas__get_project_updates with the project's ARI ID.
  3. Parse the returned JSON which contains projectId, updates (array), and highlights (array).
  4. If no updates exist, respond: "No status updates found for this project."
  5. If updates exist, display the most recent update (first in the array) formatted as:

    Latest Status Update

    • Summary: [extract text from ADF JSON by walking all text nodes]
    • Status: [status value]
      • Use these indicators: on_track = ON_TRACK, at_risk = AT_RISK, off_track = OFF_TRACK, done = DONE
    • Updated: [createdAt date]

    If there are more updates beyond the first, add: "N more status updates available."

  6. Highlights (if any exist):

    Highlights

    • [highlight summary 1]
    • [highlight summary 2]

    If no highlights, omit this section.

  7. On error, display the error message and suggest checking the project ID and Atlas MCP configuration.

ADF Parsing

Update summaries are in Atlassian Document Format (ADF) JSON. Extract plain text by recursively walking the JSON and collecting all text field values. Join them with spaces.

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.