Skip to main content
Run any Skill in Manus
with one click
nakane1chome
GitHub creator profile

nakane1chome

Repository-level view of 12 collected skills across 1 GitHub repositories, including approximate occupation coverage.

skills collected
12
repositories
1
occupation fields
3
updated
2026-04-22
repository map

Where the skills live

Top repositories by collected skill count, with their share of this creator catalog and occupation spread.

repository explorer

Repositories and representative skills

#001
claude-skills
12 skills01updated 2026-04-22
100% of creator
sandbox
Software Developers

Scaffolds a Docker "sandbox" harness into a repo so Claude Code can run in `--dangerously-skip-permissions` (YOLO) mode inside an Ubuntu container, with the project bind-mounted at /workspace and the host's ~/.claude bind-mounted for auth and session continuity. Use when the developer wants an isolated filesystem for agent writes but still wants host-visible builds, logs, and session history.

2026-04-22
dev-record
Software Developers

Record agent activity during Claude Code sessions. Captures plans, human input, agent decisions, and deviations via hooks and agent self-reporting.

2026-04-03
generator-coding
Software Developers

Template-based code generation pattern using data models, templates, and helper functions to generate repetitive interface code.

2026-04-03
no-pre-existing-failures
Software Quality Assurance Analysts & Testers

Test accountability policy. All failures belong to the current changeset. Commits must include test results. No failures on main.

2026-04-03
review-skill
Software Developers

Reviews a SKILL.md file or skill directory for quality, correctness, and alignment with Claude Code skill conventions. Use when you've written a new skill and want to check it before committing, or when evaluating an existing skill for improvements.

2026-03-22
mybadskill
Software Developers

Helps with things

2026-03-22
flesh-out
Proofreaders & Copy Markers

Transform raw/crude document drafts into structured content. Use when a document is a skeleton of ideas, notes, or stream-of-consciousness that needs generative expansion rather than review polish.

2026-02-17
review-steps
Editors

Structured review for polishing documents. Fixes language, improves clarity, checks structural consistency, and compares against best practice. Use when a draft has structure but needs a thorough review pass.

2026-02-17
Showing top 8 of 12 collected skills in this repository.
Showing 1 of 1 repositories
All repositories loaded