atlas-create
Skill0 starsChanged 4 months agoMITView on GitHub
Create one or more Atlas projects, optionally linked to a goal, tagged, and linked to Jira issues
In this repository5 other files it gives its agents.
- atlas-my-updatesSkill
- atlas-projectsSkill
- atlas-statusSkill
- atlas-tagSkill
- atlas-updateSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 3 are distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Create one or more Atlas projects.
- Very specific: line 13
Use the atlas MCP server. All tool calls use the mcp__atlas__ prefix.
- Distinctive: line 49
When the user provides a list of Jira issue keys and wants an Atlas project created for and linked to each:
- Very specific: line 69
If a create_project call returns a string starting with Error:, the project was not created (creation is the first, required step).
- Distinctive: line 70
Verify the Jira issue key / goal key is correct and visible to you
- Very specific: line 71
Check that the Atlas MCP server is configured in .mcp.json
- Very specific: line 72
Verify ~/.atlas/config.json exists with valid credentials
- Very specific: line 74
If the result is JSON with a warnings array, the project was created but one or more optional attributes did not apply — report both the …
≈ “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.
Files
Atlas Create Project
Create one or more Atlas projects. Each project takes a name and description, and can optionally be linked to a goal, given a tag, and linked to a Jira issue.
MCP Server
Use the atlas MCP server. All tool calls use the mcp__atlas__ prefix.
The create_project tool
mcp__atlas__create_project accepts:
name(required): project namedescription(optional): the "what" text describing the projectgoal(optional): a goal key (e.g.SAFET-2881) or a goal ARI — resolved by key automaticallytag(optional): a tag name — created if it doesn't already existjira_issue_key(optional): a Jira issue key (e.g.FG-6269) or a work-item ARI — resolved by key automatically
The project is created first; each optional attribute is applied as a follow-up. If an optional step fails, the project is still created and the failure is returned in a warnings array. Read the returned JSON and surface any warnings to the user.
Workflow: single project
- Gather the details.
nameis required; ask for it if not provided.description,goal,tag, andjira_issue_keyare optional — only include the ones the user wants. Preview before creating:
Preview
Name: [name] Description: [description or "None"] Goal: [goal or "None"] Tag: [tag or "None"] Jira issue: [jira_issue_key or "None"]
Create this project? (yes/no)
- On confirmation, call
mcp__atlas__create_projectwith the gathered arguments. - On success, report the new project's
key,name, and anywarnings. Include a link:https://<subdomain>.atlassian.net/o/-/s/projects/<key>if the subdomain is known, otherwise just the key.
Workflow: batch from a list of Jira issues
When the user provides a list of Jira issue keys and wants an Atlas project created for and linked to each:
- Confirm the shared conventions once, up front:
- Naming: name each project after its Jira ticket (default), or use names the user supplies. When naming after the ticket, the tool resolves the issue and its summary is available — a project named after the summary reads best.
- Description: same text for all, per-ticket, or blank.
- Goal: one goal key to link all of them to, or none.
- Tag: one tag to apply to all, or none.
Show the full plan as a table and confirm before creating anything:
Jira issue Project name Goal Tag FG-6269 ... SAFET-2881 platform - On confirmation, call
mcp__atlas__create_projectonce per ticket, passingjira_issue_keyfor each. Do not stop on the first failure — create the rest and collect results. - Report a summary table of results: each ticket, the created project key (or error), and any warnings.
Error Handling
If a create_project call returns a string starting with Error:, the project was not created (creation is the first, required step). Surface the message and suggest:
- Verify the Jira issue key / goal key is correct and visible to you
- Check that the Atlas MCP server is configured in
.mcp.json - Verify
~/.atlas/config.jsonexists with valid credentials
If the result is JSON with a warnings array, the project was created but one or more optional attributes did not apply — report both the success and the warnings.
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
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.

