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

atlas-projects

Skill0 starsChanged 4 months agoMITView on GitHub

List and browse your Atlassian Atlas projects

The file

We split this skill into the rules it gives an agent

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

  • 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. Distinctive:

    Check if the user provided project IDs as arguments to the command.

    line 17
  3. Distinctive:

    If status is missing, show "-"

    line 29
  4. Distinctive:

    If target date is missing, show "-"

    line 30
  5. Very specific:

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

    line 35
  6. Very specific:

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

    line 36

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

List the user's Atlas projects in a formatted table.

MCP Server

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

Workflow

  1. Check if the user provided project IDs as arguments to the command.
  2. If no project IDs provided, call the mcp__atlas__list_projects tool with limit: 20.
  3. If specific project IDs provided, call the mcp__atlas__get_projects tool with the list of IDs.
  4. Parse the returned JSON and format the results as a table:

    KeyNameStatusTarget Date
    PROJ-1Example ProjectON_TRACK2025-06-30
    • If status is missing, show "-"
    • If target date is missing, show "-"
  5. Show a count summary at the end: "Showing N projects"
  6. On error, display the error message clearly and suggest:
    • Check that the Atlas MCP server is configured in .mcp.json
    • Verify ~/.atlas/config.json exists with valid credentials

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.