Pedro Nauck's Skills
88 skills in three folders: the author's own for Go, React and code review, hand-picked third-party ones and 13 on marketing and pitching
- 648 ★ on the repository
- Last commit
Extended access
Why this level
- The ship-pr and git-rebase skills walk the agent through commits, rebases and publishing a pull request
- Some skills (sentry-cli, electron-release) run commands of external services
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/pedro-nauck-s-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The ship-pr and git-rebase skills walk the agent through commits, rebases and publishing a pull request
- Some skills (sentry-cli, electron-release) run commands of external services
This is third-party code. Review the repository files before installing.
What it does
Pedro Nauck's repository holds 88 skills in three folders: skills/mine with 41 of his own, skills/curated with 34 hand-picked ones and skills/marketing with 13 on marketing, business and writing. The original skills cover development. Deep-review examines a branch diff and pull requests, deslop strips traces of AI-written code from changes, golang-master and rust-best-practices set rules for Go and Rust, bubbletea teaches building terminal interfaces in Go, tanstack, react and tailwindcss drive the frontend, git-rebase works through rebase conflicts, and ship-pr and qa-execution carry changes through to a PR and verification. Some are unusual: yc-apply, vc-pitch-deck and vc-outreach prepare an application and a pitch for investors. Curated holds chosen third-party skills such as agent-browser, context7, shadcn, systematic-debugging, vitest, zod and vercel-react-best-practices. The marketing folder contains copywriting, google-ads, fundraising and humanizer.
Who it is for. Full-stack developers on TypeScript, Go or Rust who want a ready set of working habits from an experienced engineer.
Good fit when
- Before merging a branch you want a deep diff review that looks for defects and small flaws
- The agent left redundant comments, casts and nesting in the code and they need cleaning up
- A Go service is being designed with errors, contexts and goroutines under one set of rules
- You need a draft of a pitch deck or an accelerator application
Not a fit when
- The agent's context is tight: 88 skill descriptions take up room, so install one folder or one skill instead
- You work outside TypeScript, Go and Rust: PHP, Java and Swift are absent from the list
- You need skills validated by independent tests: the README lists purposes but no quality evaluation results
Example request
Run deep-review on the current branch against main and list defects by severity, then run deslopLimitations
Installing all 88 skills at once is unwise: each description lands in the agent's context, so take one folder (`skills/mine`) or a single skill with the `--skill` flag. The curated folder is assembled from third-party projects, and the repository keeps docs/upstream-skills.md. The README is oriented to Claude Code. For deep-review, benchmark and validation reports sit in docs. Rerunning the same command pulls updates from the repository.
How to disable. Delete the skill folder from `~/.claude/skills`, or remove the link if you symlinked a whole bucket. Skills added through `npx skills add` are removed with the same skills tool.
FAQ
How do I install only the author's own skills?
Run `npx skills add pedronauck/skills/skills/mine`. For the picked third-party skills use `skills/curated` and for the marketing ones `skills/marketing`.
How do mine, curated and marketing differ?
Mine holds 41 skills written by the author. Curated holds 34 chosen ones, some written locally and some taken from other projects. Marketing holds 13 skills on marketing, business and writing.
How do I install a single skill such as react?
The command `npx skills add pedronauck/skills/skills/mine --skill react` installs it from mine. By hand, `cp -r skills/mine/react ~/.claude/skills/react` is enough.
How do I update installed skills?
Rerun `npx skills add https://github.com/pedronauck/skills`. For a manual install, update your clone and copy the folders again; `skills-lock.json` records versions.
What does deep-review do?
The skill reviews a branch diff, a working tree or a pull request: automated preparation, staged rule discovery, compact per-job assessments, targeted repairs and optional publication to the PR.
Discussion
No questions or reviews yet.
Related
SkillsOver 200 skills by stack and practice: React, Next.js, Rails, Rust, Python, debugging, TDD and UI review
A code review skill across many languages and frameworks: architecture, performance, security, anti-patterns and common bugs
my-skills by akitaonrails
akitaonrails my-skills
Fabio Akita's personal set of 24 skills for Claude Code, Codex and opencode: releases, PR audits, security and fact-checking
kyy-logs code-review-skill
code-review-skill
A code review skill with four independent probes, evidence-backed findings and a merge gate derived from JSON
Catalog of 46 versioned skills for code review, releases, CI and landing pages, installed as the lstack plugin or through npx.
Dimillian Skills
Skills
A set of 16 engineering skills for agents: Apple platform work, macOS packaging, React performance, code review and refactoring
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Pedro Nauck's Skills (this card) | no | 648 | |
| Superpowers | no | 313,096 | one development process from plan to TDD, while this is a spread of separate skills by language and tool |
| Compound Engineering | no | 25,951 | a plugin with a brainstorm, plan, review loop, while this is independent skills without a shared loop |
README in short
The README describes the three folders, gives three ways to install (everything, one folder, by hand) and lists each skill with a one-line purpose and an origin badge. A separate section explains how an agent picks a skill from the description field.
README badge
Original SKILL.md
--- name: deslop description: Review a changed diff for accidental complexity or generated-code noise. Use when requested or when the diff shows those symptoms; an equivalent review of unchanged inputs need not repeat. --- # Review the Changed Diff Use the task's actual diff, including relevant working changes. Preserve unrelated edits and project compatibility requirements. Remove accidental noise introduced by this task: redundant comments, unjustified casts/suppressions, defensive branches on trusted data, duplicated helpers, and unnecessary nesting. Keep boundary validation, error handling, and required migration/deprecation adapters. Review once before final verification. A review already performed on the same diff satisfies this step; revisit only subsequent relevant edits. Avoid cleanup outside the requested scope. Report substantive changes briefly.