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

atlas-update

Skill0 starsChanged 4 months agoMITView on GitHub

Compose and post a status update to an Atlas project

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. muslewski/status-herald★ 2same name
    2. muslewski/token-oracle★ 2same 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

11 rules. About 0 are common, 4 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    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-update SAFET-2318).

    line 19
  3. Very specific:

    If a project key (not ARI ID) was provided, call mcp__atlas__list_projects with limit: 50 to resolve the ARI ID.

    line 21
  4. Very specific:

    Call mcp__atlas__get_project_updates with the project's ARI ID.

    line 25
  5. Distinctive:

    If no previous updates exist, note: "This will be the first status update for this project."

    line 29
  6. Distinctive:

    Ask the user for each field one at a time:

    line 33
  7. Distinctive:

    If any MCP tool call fails, display the error message clearly and suggest:

    line 70
  8. Distinctive:

    Verify the project key is correct

    line 71
  9. Very specific:

    Check that the Atlas MCP server is configured in .mcp.json

    line 72
  10. Very specific:

    Verify ~/.atlas/config.json exists with valid credentials

    line 73
  11. Very specific:

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

    line 77

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

Guide the user through composing and posting a status update to an Atlas project. This is an interactive workflow -- gather input step by step, confirm before posting.

MCP Server

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

Workflow

Step 1: Get the project

Check if a project key was provided as an argument (e.g., /atlas-update SAFET-2318). If not, ask the user which project to update.

If a project key (not ARI ID) was provided, call mcp__atlas__list_projects with limit: 50 to resolve the ARI ID.

Step 2: Show current status for context

Call mcp__atlas__get_project_updates with the project's ARI ID. If updates exist, show the most recent one briefly:

Current status: [status value] -- "[summary extracted from ADF]" (posted [createdAt])

If no previous updates exist, note: "This will be the first status update for this project."

Step 3: Gather update details

Ask the user for each field one at a time:

  1. Summary (required): "What's the status update? Describe what's happening with the project."
  2. Status (required, with default): "What's the project status? Options: on_track, at_risk, off_track, done (default: on_track)"
  3. Highlights (optional): "Any wins or accomplishments to highlight? You can list multiple, or skip this."

Step 4: Preview and confirm

Show a preview of the update before posting:

Preview

Project: [project key] Summary: [summary text] Status: [status value] Highlights: [list of highlights, or "None"]

Post this update? (yes/no)

Step 5: Post or abort

If the user confirms:

Call mcp__atlas__create_project_update with:

  • project_id: the ARI ID
  • summary: the user's summary text
  • status: the chosen status (e.g., "on_track")
  • highlights: JSON string array of highlight summaries (e.g., '["Shipped feature X", "Completed migration"]'), or "[]" if no highlights

On success, show: "Status update posted successfully."

If the user declines:

Respond: "Update cancelled. No changes were made."

Error Handling

If any MCP tool call fails, display the error message clearly and suggest:

  • Verify the project key is correct
  • Check that the Atlas MCP server is configured in .mcp.json
  • Verify ~/.atlas/config.json exists with valid credentials

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.

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.