builder-essential-skills
A repository for skills that are essential to my daily work
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/tamdogood-builder-essential-skills)HTML
<a href="/listings/tamdogood-builder-essential-skills"><img src="/api/listings/tamdogood-builder-essential-skills/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Install with the skills.sh CLI:
npx skills add tamdogood/skills
Install one skill from the collection:
npx skills add tamdogood/skills --skill lead
The skills.sh page for this repository is [skills.sh/tamdogood/skills](https://skills.sh/tamdogood/skills). It appears after the repository has been installed through the `skills` CLI and the skills.sh cache refreshes.
You can also use the bundled npm installer.
Install every skill for your user account:
npx @tamng0905/builder-essential-skills
Install into the repository you are currently in:
npx @tamng0905/builder-essential-skills --project
Install only one skill:
npx @tamng0905/builder-essential-skills --skill lead
Add `--project` to that command to install the selected skill into the current repository. Restart Claude Code or Codex after installation.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 324 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- <p align="center">
- <img src="assets/readme-hero.png" alt="Builder's Essential Skills, shown as an original dark atelier of connected creative tools" width="100%">
- </p>
- <p align="center">
- <strong>Builder's Essential Skills</strong><br>
- A considered collection of reusable workflows for planning, building, researching, learning, validating, writing, and reviewing with Claude Code and Codex.
- </p>
- <p align="center">
- <a href="https://www.npmjs.com/package/@tamng0905/builder-essential-skills"><img src="https://img.shields.io/npm/v/%40tamng0905%2Fbuilder-essential-skills?logo=npm&label=npm" alt="npm package version"></a>
- </p>
- <p align="center">
- <a href="#install">Install</a> ·
- <a href="#pick-a-skill">Pick a skill</a> ·
- <a href="#bring-your-own-workflow">Create a skill</a>
- </p>
- ## Install
- Install with the skills.sh CLI:
- ```bash
- npx skills add tamdogood/skills
- ```
- Install one skill from the collection:
- ```bash
- npx skills add tamdogood/skills --skill lead
- ```
- The skills.sh page for this repository is
- [skills.sh/tamdogood/skills](https://skills.sh/tamdogood/skills). It appears
- after the repository has been installed through the `skills` CLI and the
- skills.sh cache refreshes.
- You can also use the bundled npm installer.
- Install every skill for your user account:
- ```bash
- npx @tamng0905/builder-essential-skills
- ```
- Install into the repository you are currently in:
- ```bash
- npx @tamng0905/builder-essential-skills --project
- ```
- Install only one skill:
- ```bash
- npx @tamng0905/builder-essential-skills --skill lead
- ```
- Add `--project` to that command to install the selected skill into the current
- repository. Restart Claude Code or Codex after installation.
- ## Pick a skill
- <table>
- <tr>
- <td width="50%" valign="top">
- <a href="skills/lead/SKILL.md"><img src="assets/skill-banners/lead.webp" alt="lead — build and delivery skill" width="100%"></a>
- </td>
- <td width="50%" valign="top">
- <a href="skills/lead-research/SKILL.md"><img src="assets/skill-banners/lead-research.webp" alt="lead-research — research and strategy skill" width="100%"></a>
- </td>
- </tr>
- <tr>
- <td width="50%" valign="top">
- <a href="skills/async-learning-teacher/SKILL.md"><img src="assets/skill-banners/async-learning-teacher.webp" alt="async-learning-teacher — learning skill" width="100%"></a>
- </td>
- <td width="50%" valign="top">
- <a href="skills/top-one-percent/SKILL.md"><img src="assets/skill-banners/top-one-percent.webp" alt="top-one-percent — deep explanation and mastery skill" width="100%"></a>
- </td>
- </tr>
- <tr>
- <td width="50%" valign="top">
- <a href="skills/validate-market/SKILL.md"><img src="assets/skill-banners/validate-market.webp" alt="validate-market — product and market skill" width="100%"></a>
- </td>
- <td width="50%" valign="top">
- <a href="skills/paper-opportunity-radar/SKILL.md"><img src="assets/skill-banners/paper-opportunity-radar.webp" alt="paper-opportunity-radar — research forensics and opportunity discovery skill" width="100%"></a>
- </td>
- </tr>
- <tr>
- <td width="50%" valign="top">
- <a href="skills/write-blog/SKILL.md"><img src="assets/skill-banners/write-blog.webp" alt="write-blog — writing and growth skill" width="100%"></a>
- </td>
- <td width="50%" valign="top">
- <a href="skills/orwell-writing/SKILL.md"><img src="assets/skill-banners/orwell-writing.webp" alt="orwell-writing — direct writing skill" width="100%"></a>
- </td>
- </tr>
- <tr>
- <td width="50%" valign="top">
- <a href="skills/code-standards/SKILL.md"><img src="assets/skill-banners/code-standards.webp" alt="code-standards — engineering quality skill" width="100%"></a>
- </td>
- <td width="50%" valign="top">
- <a href="skills/session-profiler/SKILL.md"><img src="assets/skill-banners/session-profiler.webp" alt="session-profiler — developer tools skill" width="100%"></a>
- </td>
- </tr>
- <tr>
- <td width="50%" valign="top">
- <a href="skills/make-playbook/SKILL.md"><img src="assets/skill-banners/make-playbook.webp" alt="make-playbook — indie maker playbook skill" width="100%"></a>
- </td>
- <td width="50%" valign="top">
- <a href="skills/create-skill/SKILL.md"><img src="assets/skill-banners/create-skill.webp" alt="create-skill — skill creation workflow" width="100%"></a>
- </td>
- </tr>
- <tr>
- <td width="50%" valign="top">
- <a href="skills/create-marketing-kit/SKILL.md"><img src="assets/skill-banners/create-marketing-kit.webp" alt="create-marketing-kit — campaign copy and artwork skill" width="100%"></a>
- </td>
- <td width="50%" valign="top">
- <a href="skills/map-the-landscape/SKILL.md"><img src="assets/skill-banners/map-the-landscape.webp" alt="map-the-landscape — big-picture orientation skill" width="100%"></a>
- </td>
- </tr>
- <tr>
- <td width="50%" valign="top">
- <a href="skills/build-scenario-tests/SKILL.md"><img src="assets/skill-banners/build-scenario-tests.webp" alt="build-scenario-tests — deterministic behavior validation skill" width="100%"></a>
- </td>
- <td width="50%" valign="top">
- <a href="skills/run-smoke-tests/SKILL.md"><img src="assets/skill-banners/run-smoke-tests.webp" alt="run-smoke-tests — auditable user journey validation skill" width="100%"></a>
- </td>
- </tr>
- <tr>
- <td width="50%" valign="top">
- <a href="skills/name-your-business/SKILL.md"><img src="assets/skill-banners/name-your-business.webp" alt="name-your-business — fast naming and selective live validation skill" width="100%"></a>
- </td>
- <td width="50%" valign="top">
- <a href="skills/repo-system-map/SKILL.md"><img src="assets/skill-banners/repo-system-map.webp" alt="repo-system-map — interactive repository architecture learning skill" width="100%"></a>
- </td>
- </tr>
- </table>
- Every skill lives in `skills/<name>/SKILL.md`. Some also ship scripts,
- reference material, or agent definitions that support the workflow.
- ## Why this exists
- An AI agent is much more useful when it has a repeatable way to handle the
- work. This collection packages practical workflows as portable skills: compact
- instructions, scripts, references, and agent definitions that you can install,
- adapt, and share.
- Use the whole collection, or take only the skills your team needs.
- ## Local install
- Use the local scripts only when you are installing from a cloned checkout.
- From the repository root, install every skill for the current user:
- ```bash
- ./install.sh
- ```
- The `npx` command installs the same files as the scripts below. It supports
- macOS, Linux, and Windows wherever Node.js 18 or newer is available.
- On Windows:
- ```powershell
- ./install.ps1
- ```
- Restart Claude Code or Codex, then invoke a skill in plain English:
- ```text
- /lead Build the smallest version of this feature and open a PR.
- $async-learning-teacher Teach me this paper step by step: https://arxiv.org/abs/...
- $map-the-landscape Show me how this repository fits together.
- $paper-opportunity-radar Audit this topic's buried research for credible opportunities.
- ```
- Want to try the collection inside one repository first? Install it locally
- instead:
- ```bash
- ./install.sh --project
- ```
- ```powershell
- ./install.ps1 -Project
- ```
- The project install uses `.claude/skills` and `.codex/skills`, so it stays
- with that repository rather than changing your user-level setup.
- ## What gets installed
- The installers copy each folder in `skills/` to the right location for your
- agent runtime.
- | Install mode | Claude Code | Codex |
- | --- | --- | --- |
- | User | `~/.claude/skills` | `${CODEX_HOME:-~/.codex}/skills` |
- | Current project | `.claude/skills` | `.codex/skills` |
- You will need Claude Code and/or Codex, depending on which agent you use. Some
- bundled deterministic tools, including `session-profiler`, require Python 3.
- ## Go deeper
- ### Native-agent orchestration
- `lead` and `lead-research` use the subagent tools provided by whichever runtime
- invokes them. They probe concurrency, isolation, messaging, shell, write, and web
- capabilities at the start of a run, then assign work by role. There are no model
- IDs or provider CLI commands to configure when switching between Codex and
- Claude Code. A runtime without native subagent delegation stops instead of
- letting the orchestrator write code or perform research itself.
- ### Profile an agent session
- After installation, point `SP` at the wrapper for Hermes:
- ```bash
- SP="${HERMES_HOME:-$HOME/.hermes}/skills/session-profiler/scripts/sp"
- ```
- Then explore your sessions:
- ```bash
- $SP list --provider hermes --n 20
- $SP info <session-id-or-jsonl-path>
- $SP parse <session-id-or-jsonl-path>
- $SP brief
- $SP agent-summary
- $SP costs
- $SP slowest-tools --n 20
- $SP errors
- $SP turns
- ```
- Generate richer artifacts:
- ```bash
- $SP toc
- $SP review
- $SP trace
- ```
- `brief` writes a scan-friendly `brief.md` with headline metrics, standout slow
- paths or failures, a prompt trail or TOC storyline, and an agent scoreboard. The
- Perfetto trace adds an overview lane, labeled TOC phases, per-agent work lanes,
- prompt lanes, and cumulative token/cost counters.
- Cost reports are estimates based on public model pricing, not billing records.
- Session files and traces can include prompts, code, file paths, and other
- sensitive project context. Review them before sharing.
- ## Repository map
- ```text
- skills/ The skill collection
- <skill>/SKILL.md Each skill's entry point and workflow
- assets/readme-hero.png README banner
- install.sh macOS/Linux installer
- install.ps1 Windows installer
- package.json npm package metadata and npx entrypoint
- bin/builder-essential-skills.js cross-platform npx installer
- ```
- ### Publish the installer
- Choose an available npm package name in `package.json`, authenticate with npm,
- then publish from the repository root:
- ```bash
- npm login
- npm publish --access public
- ```
- npm requires either 2FA enabled on the account, followed by the one-time code
- requested by `npm publish`, or a granular access token with read/write access
- and **Bypass two-factor authentication** enabled. For a local interactive
- publish, enabling 2FA and running `npm login` again is the simplest option.
- Never commit an access token; use npm's login flow or a secure CI secret.
- After publishing, users can run `npx @tamng0905/builder-essential-skills` without cloning the
- repository. Bump the version in `package.json` for each subsequent publish.
- ## Bring your own workflow
- Start with one folder:
- ```text
- skills/my-skill/
- SKILL.md
- ```
- Give `SKILL.md` clear frontmatter and a focused workflow:
- ```markdown
- ---
- name: my-skill
- description: Explain when an agent should use this skill.
- ---
- # My Skill
- Write the workflow, rules, examples, and expected output here.
- ```
- Keep skills easy to move between projects:
- - Avoid hard-coding a company, repository, branch, or tool unless the skill is intentionally private.
- - Put reusable scripts beside the skill instead of relying on global shell state.
- - Include request examples that show exactly when the skill should run.
- - Create `assets/skill-cards/<name>.svg` for each new skill and add it to the
- README's "Pick a skill" table.
- - Never put credentials, tokens, or private data in a skill folder.
- Re-run the installer after adding or changing a skill:
- ```bash
- ./install.sh
- ```
- ## License
- MIT. See [LICENSE](LICENSE).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.