readme-writer
Write READMEs for software projects. The skill should be used when writing or revising a README or README.md file.
Browse published AI skills maintained by nateberkopec. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
23Repository stars across indexed skills
981Repository forks
33Average repository stars per indexed skill
43Repository stars may repeat across skills from the same repository.
Write READMEs for software projects. The skill should be used when writing or revising a README or README.md file.
This skill should be used when users request comprehensive, in-depth research on a topic that requires detailed analysis similar to an academic journal or whitepaper. The skill conducts multi-phase research usi...
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or to...
This skill should be used when setting up or running the Ralph autonomous coding loop that iterates through stories, runs tests, commits, and logs learnings.
This skill should be used when users want to manage windows on macOS using AeroSpace, an i3-like tiling window manager. Use for both ad-hoc window management requests ("move this window to workspace 2", "tile t...
Generate, edit, and restore images using Gemini CLI with the Nano Banana extension. Use when users request image generation, edits, icons, patterns, diagrams, or visual storytelling.
Install standardized flog/flay Rake tasks and a pre-commit hook that runs bundle exec rake for Ruby projects. Use when adding or normalizing code complexity and duplication checks.
This skill should be used when users want to migrate from .env files to fnox with 1Password (or another secret provider). It covers installing fnox, creating 1Password items, configuring fnox.toml, and integrat...
This skill should be used when users request code review, refactoring, or code quality improvements for Ruby codebases. Apply Sandi Metz's four rules for writing maintainable object-oriented code - classes unde...
This skill should be used when users want to validate or critique an argument by extracting premises, surfacing hidden assumptions, checking logical validity, optionally formalizing in Lean, and researching pre...
Walk through all GTD inboxes and process each item to zero. Use for regular inbox processing or when user says "help me process my inbox". Integrates clarify-item, assign-context, and check-delegatability skill...
Help user decide what to work on next based on GTD's four criteria - context, time available, energy level, and priority. Use when user asks what to do or seems stuck on choosing. Handles rejection via refine-n...
Quick daily scan of calendar and next actions to stay on top of the day. Use at the start of each day or when user asks what's happening today. Shows time-sensitive items and context-appropriate actions.
Convert a multi-step item into a proper GTD project with clear outcome and first next action. Use when an item requires more than one action to complete. Creates Todoist project, defines done, identifies first...
Document how to read and edit calendars with specific semantics (Fastmail, Schedule, shared calendars). Use when adding, editing, or summarizing calendar events.
Manage the GTD tickler file via the Tickler calendar (all-day events that trigger Todoist inbox items).
Guide user through the complete GTD weekly review in three phases - Get Clear, Get Current, Get Creative. Use when user wants to do their weekly review. This is the most critical GTD maintenance ritual.
Turn a nebulous or complex item into a fully-formed GTD project with clear outcome, first next action, and supporting materials. Use when something needs to be broken down into a project with multiple actions.
Interview flow to understand what an inbox item is and determine its actionability. Use when processing inbox items to decide if they're actionable and what the next physical action is. Routes non-actionable it...
File reference material into the filesystem (default ~/Documents/Reference). Use when routing non-actionable items to reference, cleaning up a filesystem inbox, or migrating reference material from another sync...
Determine if an action can and should be delegated to someone else. Use when processing actions to identify delegation opportunities. Outputs whether item is delegatable, suggested delegate, and waiting-for for...
Handle refinement of next actions when user rejects suggestions, wants to change context, defer, delegate, or break down further. Use when a suggested action doesn't fit or circumstances change.
Suggest and assign context tags to actions based on where/how they can be done. Use after clarifying an item to determine what contexts (location, tool, energy level) are needed. Fetches available contexts from...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.