Repo Hygiene Scan and Fix
QwenLM/qwen-code
Scheduled CI skill that scans a repository for small, certain docs, test and code hygiene issues and fixes them on one branch with a commit per finding.
Generate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy.
Install Atlas Onboard
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill atlas-onboard -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace atlas-onboard --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-onboard .claude/skills/atlas-onboard && rm -rf skills-srcUse ~/.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/
Install the "atlas-onboard" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/atlas-onboard into .claude/skills/atlas-onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atlas-onboard", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/atlas-onboardType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill atlas-onboard -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace atlas-onboard --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/atlas-onboard .agents/skills/atlas-onboard && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "atlas-onboard" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/atlas-onboard into .agents/skills/atlas-onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atlas-onboard", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill atlas-onboard -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace atlas-onboard --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/atlas-onboard .cursor/skills/atlas-onboard && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "atlas-onboard" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/atlas-onboard into .cursor/skills/atlas-onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atlas-onboard", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path plugins/ai-agency/tonone/skills/atlas-onboard--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill atlas-onboard -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace atlas-onboard --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/atlas-onboard .gemini/skills/atlas-onboard && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "atlas-onboard" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/atlas-onboard into .gemini/skills/atlas-onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atlas-onboard", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace atlas-onboardInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill atlas-onboard -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/atlas-onboard .github/skills/atlas-onboard && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "atlas-onboard" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/atlas-onboard into .github/skills/atlas-onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atlas-onboard", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill atlas-onboard -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace atlas-onboard --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/atlas-onboard .opencode/skills/atlas-onboard && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "atlas-onboard" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/ai-agency/tonone/skills/atlas-onboard into .opencode/skills/atlas-onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "atlas-onboard", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
atlas-onboard- GitHub stars
- 2.8k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 292 words
- Files
- 2
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Generate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy.
- Works in 5 steps: Detect Environment → Read the Codebase Thoroughly → Write the Onboarding Document → …
- Asked for onboarding docs
- SKILL.md covers Steps and Delivery
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Atlas Onboard is an agent skill from jeremylongshore/tons-of-skills-marketplace. Generate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy. Written for day-one engineers who know nothing. Use when asked for "onboarding docs", "new engineer guide", "how to get started", or "developer setup".
Its SKILL.md is about 1.1k 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 DevOps & Cloud. 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 for onboarding docs
- New engineer guide
- How to get started
- Developer setup
Example prompts
- “onboarding docs”
- “new engineer guide”
- “how to get started”
- “/atlas-onboard”
Requirements
- Docker
- 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.
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:
ReadWriteEditBashGlobGrepWebFetchWebSearchTaskTodoWrite
…and 1 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 Onboard loads about 1.1k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 292 words of instructions outside code blocks.
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.
- NoteMentions a .env fileSKILL.md:70
3. Set up environment: `cp .env.example .env` and fill in [what] - 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). 292 words, ~1,081 tokens.
Download SKILL.mdSave it as
.claude/skills/atlas-onboard/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- atlas-onboard
- description
- Generate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy. Written for day-one engineers who know nothing. Use when asked for "onboarding docs", "new engineer guide", "how to get started", or "developer setup".
- 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
Generate Onboarding Documentation
You are Atlas — the knowledge engineer from the Engineering Team. Write for the person on day 1 who knows nothing about this project.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 0: Detect Environment
Scan the workspace for project indicators:
README.md— existing readme (assess quality and freshness)CONTRIBUTING.md— existing contributor guidedocs/— existing documentation directorydocs/onboarding.md— existing onboarding docdocs/adr/— existing ADRs to reference- Package files, Dockerfiles, CI configs — to understand the setup process
Determine where onboarding docs should live based on project conventions.
Step 1: Read the Codebase Thoroughly
Understand the full picture:
- What it does — read README, main entry points, and key modules to understand purpose
- Architecture — identify services, data stores, external dependencies (reference existing diagrams if available)
- Setup requirements — language runtimes, databases, environment variables, API keys, external services
- Build and run — how to install dependencies, build, run locally, run tests
- Deploy — how and where it deploys, what CI/CD exists
- Key decisions — check for ADRs, technical design docs, or significant comments
Step 2: Write the Onboarding Document
Structure for a day-one engineer:
# [Project Name] — Getting Started
## What This Project Does
[2-3 sentences. No jargon. What problem does it solve and for whom?]
## Architecture Overview
[Brief description with diagram reference if available.
Link to detailed architecture docs if they exist.]
## Local Setup
### Prerequisites
- [runtime/tool] version [X] — install via [method]
- [database] — install via [method]
- [other dependency]
### Step-by-Step Setup
1. Clone the repo: `git clone ...`
2. Install dependencies: `[command]`
3. Set up environment: `cp .env.example .env` and fill in [what]
4. Set up database: `[command]`
5. Run the app: `[command]`
6. Verify it works: open [URL] or run [test command]
## Where Things Live
| Directory | What's There |
| --------- | ------------- |
| `src/` | [description] |
| `tests/` | [description] |
| ... | ... |
## Key Technical Decisions
- [Decision] — [why, or link to ADR]
- [Decision] — [why, or link to ADR]
## How to Deploy
[Brief description of deploy process, or link to deploy docs]
## Common Tasks
- **Run tests:** `[command]`
- **Add a migration:** `[command]`
- **[other common task]:** `[command]`
## Who to Ask
- [Area] — [person/team or "see docs/[file]"]Step 3: Verify Setup Steps
Read the actual config files to confirm:
- The install commands are correct for the detected package manager
- Required environment variables are listed (check
.env.example, docker-compose, CI configs) - The run command actually matches the project's scripts/config
Do not guess setup steps — verify them from project files.
Step 4: Save and Present
Save to docs/onboarding.md or CONTRIBUTING.md based on project conventions.
## Onboarding Doc Created
**Saved to:** [path]
**Setup steps:** [N] steps verified against project config
### Covers
- What the project does
- Architecture overview
- Local setup (step-by-step)
- Directory guide
- Key technical decisions
- Deploy process
- Common tasks
### Gaps Found
- [anything missing — e.g., no .env.example, unclear deploy process]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-onboard of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- .claude-plugin/plugin.json
Open the folder on GitHubat commit cfae287
Compare with similar skills
Atlas Onboard 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Atlas Onboard this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.1k | Automated safety check: Notes | MIT | |
| Repo Hygiene Scan and FixQwenLM/qwen-code | 28k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Bash Defensive Patternspromovaweb/setupvibe | 103 | 14 repos | ~572 | Automated safety check: Pass | GPL-3.0 | |
| Terravision Cloud Diagramspatrickchugh/terravision | 1.6k | — | ~5.6k | Automated safety check: Notes | AGPL-3.0-only | |
| NGINX Ingress Controller Feature Checklistsnginx/kubernetes-ingress | 5.1k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| GreptimeDB Release RunbookGreptimeTeam/greptimedb | 6.7k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Bash Defensive Patterns
promovaweb/setupvibe
Master defensive Bash programming techniques for production-grade scripts.
Terravision Cloud Diagrams
patrickchugh/terravision
Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision.
NGINX Ingress Controller Feature Checklists
nginx/kubernetes-ingress
Gives step-by-step checklists for adding Ingress annotations, VirtualServer fields and Helm values to the NGINX Kubernetes Ingress Controller, with common gotchas.
GreptimeDB Release Runbook
GreptimeTeam/greptimedb
Runbook for publishing a GreptimeDB version: pick the release branch, verify the Cargo version, then tag, create the GitHub release and open the docs note PR.
Motel Debug
kitlangton/motel
Debug applications with motel, a local OpenTelemetry ingest and query server.
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming 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.
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.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
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.
Related
Categories
Questions about Atlas Onboard
What does Atlas Onboard do?
Generate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy. Atlas Onboard is an agent skill from jeremylongshore/tons-of-skills-marketplace. Generate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy.
When should I use Atlas Onboard?
Atlas Onboard fits situations like: asked for onboarding docs; new engineer guide; how to get started; developer setup.
How do I install Atlas Onboard in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill atlas-onboard -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/atlas-onboard in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/atlas-onboard in your project. Claude Code loads it when a task matches its description.
How do I install Atlas Onboard in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill atlas-onboard -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/atlas-onboard in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/atlas-onboard in your project. Codex loads it when a task matches its description.
Can I use Atlas Onboard 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-onboard -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-onboard, .gemini/skills/atlas-onboard, .github/skills/atlas-onboard and .opencode/skills/atlas-onboard in your project.
What does Atlas Onboard need to run?
SKILL.md names no scripts, command-line tools or credentials: Atlas Onboard is instructions for the agent only. Our summary lists: Docker. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion.
Does Atlas Onboard access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Atlas Onboard safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file; 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 Onboard use?
Atlas Onboard 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 Onboard use?
About 1.1k tokens (SKILL.md is roughly 4.3k 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 Onboard?
Skills that share tags, products or a category with Atlas Onboard: Repo Hygiene Scan and Fix (QwenLM/qwen-code, 28k stars), Bash Defensive Patterns (promovaweb/setupvibe, 103 stars), Terravision Cloud Diagrams (patrickchugh/terravision, 1.6k stars) and NGINX Ingress Controller Feature Checklists (nginx/kubernetes-ingress, 5.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Atlas Onboard?
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.