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

atlas-my-updates

Skill0 starsChanged 4 months agoMITView on GitHub

List status updates for all Atlas projects you own or contribute to

The file

We split this skill into the rules it gives an agent

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

  • 3

    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:

    Call mcp__atlas__list_projects with limit: 50 to get all active projects.

    line 17
  3. Distinctive:

    If a project has highlights, append them:

    line 35
  4. Very specific:

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

    line 49

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

Show the latest status updates for all projects where the authenticated user is an owner or contributor.

MCP Server

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

Workflow

  1. Call mcp__atlas__list_projects with limit: 50 to get all active projects.
  2. Parse the returned JSON array. Filter for projects where:
    • The owner field contains "Razvan Balazs"
    • OR the members array contains "Razvan Balazs"
  3. For each matching project, call mcp__atlas__get_project_updates with the project's id (ARI format).
  4. Format the output grouped by project, showing the latest 3 updates per project:

    [Project Name] [key] [status]

    Role: Owner | Contributor (Owner: [name]) | Due: [dueDate]

    • [date] [status]: [summary text]
    • [date] [status]: [summary text]
    • [date] [status]: [summary text]
  5. If a project has highlights, append them:

    Highlights:

    • [highlight summary 1]
    • [highlight summary 2]
  6. Show a summary at the end:
    • Total projects: N (M owned, K contributing)
    • Projects needing attention (at_risk or off_track or due within 2 weeks)
  7. On error, display the error message and suggest checking the Atlas MCP server 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. Ignore media, emoji, and other non-text nodes.

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.