New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Atlas Adr

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted.

MITAuto-check: notesDevelopment

Install Atlas Adr

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill atlas-adr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace atlas-adr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/atlas-adr .claude/skills/atlas-adr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
atlas-adr
GitHub stars
2.8k
Token cost
~1.6k tokens
SKILL.md length
539 words
Files
2
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted.

  • Works in 5 steps: Detect ADR Conventions → Gather the Decision Context → Write the ADR → …
  • Asked to write an ADR
  • SKILL.md covers Operating Principle, Step 0: Detect ADR Conventions, Step 1: Gather the Decision… and Step 2: Write the ADR, plus 3 more sections
  • Calls git

What it does

Atlas Adr is an agent skill from jeremylongshore/tons-of-skills-marketplace. Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `.claude-plugin/plugin.json`).

It sits in Development, covering Architecture decision records. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Asked to write an ADR
  • Document this decision
  • Why did we choose X

Example prompts

  • “write an ADR”
  • “document this decision”
  • “why did we choose X”
  • “/atlas-adr”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Detect ADR Conventions
  2. Gather the Decision Context
  3. Write the ADR
  4. Save the ADR
  5. Output Summary (CLI)

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash
    • Glob
    • Grep
    • WebFetch
    • WebSearch
    • Task
    • TodoWrite

    …and 1 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Atlas Adr loads about 1.6k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 539 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 539 words, ~1,622 tokens.

Download SKILL.mdSave it as .claude/skills/atlas-adr/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
atlas-adr
description
Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".
allowed-tools
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
version
0.6.4
author
tonone-ai <hello@tonone.ai>
license
MIT

Write an Architecture Decision Record

You are Atlas — the knowledge engineer from the Engineering Team. Produce a complete, honest ADR — not a template exercise, not a coaching session. Given a decision, write the record.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Operating Principle

ADR is an explanation-type document. Its only job: preserve the context of a decision so future engineers understand why the system is shaped as it is — and don't unknowingly undermine choices that had good reasons, or re-fight battles already settled.

What makes ADRs fail in practice:

  • Thin context. "We needed a database" is not context. Context is constraints, team state, scale, timeline, existing stack.
  • Fake alternatives. One obvious loser next to the winner is theater. List the real contenders.
  • No acknowledged downsides. Every decision has trade-offs. An ADR with no consequences is a press release, not a decision record.
  • Written too late. Writing an ADR six months after the decision — write what you actually remember, don't reconstruct a cleaner story than what happened.

One ADR per decision. Short and honest beats comprehensive and polished.

Step 0: Detect ADR Conventions

Before writing, check for existing ADR structure:

  • docs/adr/, doc/adr/, docs/decisions/, docs/architecture/decisions/
  • Files matching NNNN-*.md — determine the next sequence number
  • .adr-dir — adr-tools config pointing to a custom location
  • Any ADR index or README in the ADR directory

If ADRs already exist, read 1–2 to match format and tone. If none exist, create docs/adr/ and start at 0001.

Step 1: Gather the Decision Context

Determine what was decided and why it needed deciding:

  • From the conversation — if the user described the decision, use that. Ask one clarifying question if context is genuinely thin: "What constraints or alternatives shaped this choice?"
  • From the codebase — if asked to document a recent decision, read git log --oneline -20, check recent diffs, read the relevant service or config. The code already reflects the decision; reconstruct why from the evidence.
  • Don't over-interview. If you have enough to write an honest ADR, write it. You can note gaps in the Context section.
Show full SKILL.md (193 more words)Show less

Step 2: Write the ADR

One page. Concrete. Honest about trade-offs.

markdown
# [NNNN]. [Title — short, imperative phrase: "Use PostgreSQL for transactional data"]

**Date:** YYYY-MM-DD
**Status:** [Proposed | Accepted | Deprecated | Superseded by ADR-NNNN]

## Context

[2–4 sentences. What situation forced this decision? What constraints existed?
Be specific: scale, team expertise, timeline, existing stack, cost, operational burden.
"We needed a way to store data" is not context. This is the most important section.]

## Decision

[1–2 sentences. What did we decide? State it plainly.
No hedging. If the decision was "use PostgreSQL on RDS", say exactly that.]

## Alternatives Considered

### [Option A — the real runner-up, not a strawman]

**Pros:** [concrete advantages — performance, operational simplicity, cost, team familiarity]
**Cons:** [concrete disadvantages]
**Why not:** [one sentence — the specific reason this lost to the chosen option]

### [Option B]

**Pros:** ...
**Cons:** ...
**Why not:** ...

## Consequences

**What becomes easier:**

- [concrete benefit — e.g., "ACID transactions for multi-table writes are handled by the DB, not application code"]

**What becomes harder or more expensive:**

- [concrete trade-off — e.g., "Horizontal write scaling requires sharding or a read-replica pattern"]
- [another trade-off]

**What this decision constrains:**

- [downstream implications — e.g., "Services that need this data must go through the API layer, not query the DB directly"]
Calibration rules
  • Context: If you can replace the context with any other project's context and it still reads fine, it's too generic. Rewrite it with the specific constraints that applied here.
  • Alternatives: Minimum 2. If there was genuinely only one option, say that explicitly — "we evaluated X but the team had no operational experience with it and the timeline was 3 weeks."
  • Consequences: Include at least one downside. If there are no downsides, you haven't thought hard enough or this wasn't actually a decision worth an ADR.
  • Length: One page. If it's longer, you're writing an RFC, not an ADR. Split it.

Step 3: Save the ADR

  • Filename: NNNN-short-kebab-title.md — e.g., 0004-use-postgresql-for-transactional-data.md
  • Save to the detected or created ADR directory
  • If an index.md or README.md exists in the ADR directory, append the new entry: | [NNNN] | [Title] | [Status] | [Date] |

Step 4: Output Summary (CLI)

┌─ ADR Written ───────────────────────────────────────────┐
│ ADR-[NNNN]: [Title]                                     │
│ Status: [Accepted/Proposed]   Date: [YYYY-MM-DD]        │
│ Saved: [path]                                           │
├─────────────────────────────────────────────────────────┤
│ Decision                                                │
│   [One sentence summary of what was decided]            │
├─────────────────────────────────────────────────────────┤
│ Key trade-off                                           │
│   [The most important consequence to be aware of]       │
├─────────────────────────────────────────────────────────┤
│ Alternatives considered                                 │
│   [Option A] — [why not, one phrase]                    │
│   [Option B] — [why not, one phrase]                    │
└─────────────────────────────────────────────────────────┘

Delivery

If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in plugins/ai-agency/tonone/skills/atlas-adr of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • .claude-plugin/plugin.json

Open the folder on GitHubat commit cfae287

Compare with similar skills

Atlas Adr next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Atlas Adr compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Atlas Adr this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.6kAutomated safety check: NotesMIT
PR Design DocOpenHands/OpenHands91k—~2.4kAutomated safety check: PassMIT
Cto AdvisorIbrahim-3d/orchestrator-supaconductor3814 repos~2.4kAutomated safety check: PassMIT
Domain Modelingbrim-borium/spotify_sdk1667 repos~806Automated safety check: PassApache-2.0
Architecture DecisionDonchitos/Claude-Code-Game-Studios26k—~1.7kAutomated safety check: PassMIT
Improve Codebase Architectureywwynm/EverythingDone14415 repos~1.3kAutomated safety check: PassGPL-3.0

Similar skills

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    91k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Cto Advisor

    Ibrahim-3d/orchestrator-supaconductor

    Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.

    381 GitHub starsUsed in 4 repos~2.4k tokens
    DevelopmentAuto-check passed

  • Domain Modeling

    brim-borium/spotify_sdk

    Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.

    166 GitHub starsUsed in 7 repos~806 tokens
    DevelopmentAuto-check passed

  • Architecture Decision

    Donchitos/Claude-Code-Game-Studios

    Create an ADR documenting a technical decision: context, alternatives considered, consequences.

    26k GitHub stars~1.7k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Improve Codebase Architecture

    ywwynm/EverythingDone

    Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.

    144 GitHub starsUsed in 15 repos~1.3k tokens
    DevelopmentAuto-check passed

  • Design Doc Mermaid

    SpillwaveSolutions/design-doc-mermaid

    Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.

    176 GitHub starsUsed in 1 repo~5.6k tokens
    DevelopmentAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Atlas Adr

What does Atlas Adr do?

Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Atlas Adr is an agent skill from jeremylongshore/tons-of-skills-marketplace. Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted.

When should I use Atlas Adr?

Atlas Adr fits situations like: asked to write an ADR; document this decision; why did we choose X.

How do I install Atlas Adr in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill atlas-adr -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/atlas-adr in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/atlas-adr in your project. Claude Code loads it when a task matches its description.

How do I install Atlas Adr in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill atlas-adr -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/atlas-adr in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/atlas-adr in your project. Codex loads it when a task matches its description.

Can I use Atlas Adr in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill atlas-adr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/atlas-adr, .gemini/skills/atlas-adr, .github/skills/atlas-adr and .opencode/skills/atlas-adr in your project.

What does Atlas Adr need to run?

Going by SKILL.md and its folder, Atlas Adr needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion.

Does Atlas Adr access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Atlas Adr safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Atlas Adr use?

Atlas Adr is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Atlas Adr use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Atlas Adr?

Skills that share tags, products or a category with Atlas Adr: PR Design Doc (OpenHands/OpenHands, 91k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 381 stars), Domain Modeling (brim-borium/spotify_sdk, 166 stars) and Architecture Decision (Donchitos/Claude-Code-Game-Studios, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Atlas Adr?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.