Skip to content
Back to search

engineer-skills

MarketplaceWorks with Claude CodeGitHub

Nate's engineering skills for Claude Code.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/nathan-nunana--engineer-skills/badge.svg)](/listings/nathan-nunana--engineer-skills)

HTML

<a href="/listings/nathan-nunana--engineer-skills"><img src="/api/listings/nathan-nunana--engineer-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.

From GitHub:

claude plugin marketplace add nathan-nunana/engineer-skills
claude plugin install engineer@engineer-skills

From a local clone, to try changes before pushing:

claude plugin marketplace add ~/Projects/engineer-skills
claude plugin install engineer@engineer-skills

Skills load at session start, so restart Claude Code after installing or updating. To update later, run `claude plugin marketplace update engineer-skills`, then restart.

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.

.claude-plugin/marketplace.json · Manifest · 14 lines
  1. {
  2. "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  3. "name": "engineer-skills",
  4. "description": "Nate's engineering skills for Claude Code.",
  5. "owner": { "name": "Nate" },
  6. "plugins": [
  7. {
  8. "name": "engineer",
  9. "description": "Docs, architecture diagrams, system design, security review, code review, testing strategy, incidents, scrum and communication.",
  10. "source": "./",
  11. "category": "productivity"
  12. }
  13. ]
  14. }
README.md · README · 58 lines
  1. # Engineer skills
  2. Claude Code skills for the parts of software engineering that aren't writing code: documentation, architecture
  3. diagrams, system design, security review, code review, testing strategy, incidents, Scrum and communication.
  4. The repo is a Claude Code plugin and its own marketplace, so one install gives you every skill, and Claude loads each
  5. one only when a request calls for it.
  6. ## Install
  7. From GitHub:
  8. ```sh
  9. claude plugin marketplace add nathan-nunana/engineer-skills
  10. claude plugin install engineer@engineer-skills
  11. ```
  12. From a local clone, to try changes before pushing:
  13. ```sh
  14. claude plugin marketplace add ~/Projects/engineer-skills
  15. claude plugin install engineer@engineer-skills
  16. ```
  17. Skills load at session start, so restart Claude Code after installing or updating. To update later, run
  18. `claude plugin marketplace update engineer-skills`, then restart.
  19. ## Skills
  20. | Skill | Use it for |
  21. |---|---|
  22. | `technical-docs` | READMEs, ADRs, runbooks, API docs, changelogs and how-to guides. |
  23. | `architecture-diagrams` | C4, sequence, deployment, data-flow, ER and state diagrams as Mermaid code. |
  24. | `system-design` | Design docs and RFCs: requirements, estimates, options and trade-offs, rollout. |
  25. | `security-review` | Threat models (STRIDE) and security reviews of designs and code changes. |
  26. | `code-review` | Reviewing pull requests, and preparing your own for review. |
  27. | `testing-strategy` | Test plans, choosing test levels, test doubles and fixing flaky tests. |
  28. | `incident-response` | Running an incident, status updates and blameless postmortems. |
  29. | `scrum-master` | Sprint planning, daily scrum, refinement, reviews, retros and Scrum metrics. |
  30. | `engineering-communication` | Status updates, escalations, estimates, 1:1s, feedback and a brag document. |
  31. | `skill-authoring` | Writing a new skill for this repo, or fixing one that misfires. |
  32. Each skill triggers from what you ask ("draw the architecture", "run a retro", "review this PR"). You can also
  33. call one directly with `/engineer:<skill>`, for example `/engineer:scrum-master`.
  34. ## Adding skills
  35. - `skills/skill-authoring/references/creating-skills.md`: how skills work and the standard every skill here follows.
  36. - `docs/skill-backlog.md`: skills worth adding later, each with a short brief.
  37. - `skills/skill-authoring/templates/SKILL.md`: the skeleton for a new skill.
  38. - `scripts/validate.sh`: checks every skill's frontmatter, size and links. Run it before committing.
  39. The quickest way to add one is to ask Claude: "make a `<name>` skill that …". The `skill-authoring` skill walks
  40. through it.
  41. ## License
  42. MIT. See `LICENSE`.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.