Skip to main content
Run any Skill in Manus
with one click
GitHub repository

skills

skills contains 12 collected skills from nateslabach, with repository-level occupation coverage and site-owned skill detail pages.

skills collected
12
Stars
4
updated
2026-05-26
Forks
0
Occupation coverage
5 occupation categories · 100% classified
repository explorer

Skills in this repository

brutal-truth
writers-and-authors

Disables the AI's default hedging, diplomatic softening, and social-nicety layers to deliver cold, unfiltered, consequentialist analysis on any topic. Use when the user wants the AI's actual assessment without padding, regardless of how harsh or uncomfortable the honest answer is.

2026-05-26
token-maxxing
software-developers

Generates as many digits of pi as possible and writes them into files inside a tokenMaxxing/ folder. Use when the user asks to token-maxx, fill a file with pi digits, test agent output throughput, or generate N pi files sequentially or in parallel.

2026-05-21
human-writing
writers-and-authors

Strips AI fingerprints from written text by enforcing banned vocabulary, forbidden sentence structures, and authentic prose patterns. Use when writing articles, documentation, social content, emails, or any text that should read as human-authored rather than AI-generated.

2026-05-21
react-component
software-developers

Generates complete, production-ready React/TypeScript components using Tailwind CSS. Use when building UI components in a React or Next.js project that requires TypeScript, Tailwind styling, and accessible interactions.

2026-05-21
css-reset
web-developers

Applies a modern CSS reset covering box-sizing, margin removal, text rendering, media defaults, and root stacking context. Use when starting a new web project, creating a global stylesheet, or when the codebase lacks sensible CSS defaults.

2026-05-21
code-review
software-quality-assurance-analysts-and-testers

Conducts a structured 3-phase code review — understanding intent, cataloguing issues by severity, and stress-testing with adversarial questions. Use when reviewing a code diff, pull request, or snippet for correctness, edge cases, security issues, and merge readiness.

2026-05-21
vibe-audit
software-quality-assurance-analysts-and-testers

Runs a comprehensive 20-point code quality audit on a "vibe-coded" codebase that was shipped fast and now needs hardening. Use this skill whenever the user mentions vibe coding, vibe audit, code audit, code review, code cleanup, hardening a prototype, productionizing a codebase, technical debt cleanup, or asks Claude to "audit my code", "review my codebase", "clean up my project", or check a freshly-shipped project for common quality issues. Also use when a user shares a repo and asks what's wrong with it or how to make it production-ready.

2026-05-21
engineering-judgment
software-developers

Applies Chesterton's Fence, Occam's Razor, the Peter Principle, and Dunning-Kruger to technical decisions. Use before refactoring, architectural changes, or any task where changing existing behavior carries risk or requires judgment about what the user actually needs.

2026-05-21
response-discipline
management-analysts-131111

Applies Parkinson's Law, the Pareto Principle, and Goodhart's Law to produce tight, high-impact responses. Use when you want the agent to cut padding, lead with what matters, and avoid optimizing for appearance over substance.

2026-05-21
prisma
software-developers

TypeScript and Prisma ORM best practices for schema design, type-safe queries, migrations, and error handling. Use when writing Prisma schemas, building database access layers, or debugging query performance in TypeScript projects.

2026-05-21
pushback
management-analysts-131111

Stress-tests ideas by surfacing assumptions, counterarguments, and confidence gaps. Use when evaluating claims, proposals, plans, or decisions that need rigorous intellectual scrutiny.

2026-05-21
depth-ui
software-developers

Applies depth-driven layered color and shadow principles to elevate average UI into polished, readable interfaces for both light and dark themes. Use when improving or reviewing UI components, setting up a design token system, applying consistent depth and shadow to an interface, or making a flat or inconsistent UI feel more refined without a full redesign.

2026-05-21