Close the Week in 30
A thirty-minute weekly shutdown ritual. Use every Friday afternoon when open loops are stacking up.
Browse
A skill is a short instruction file — a repeatable procedure an agent follows step by step, not a one-off prompt. Browse what the community has written, copy any of it into your vault, and credit stays with the author.
skills/<category>/<name>/SKILL.md
No skills match that. Try clearing the search or picking another category.
A thirty-minute weekly shutdown ritual. Use every Friday afternoon when open loops are stacking up.
Turn blank screens into a clear next action. Use when a list, inbox, or dashboard can be empty for a new user.
Rewrite a draft so a new teammate understands it. Use when editing docs, release notes, or a talk outline.
Write alerts that fire on user-visible symptoms instead of internal hunches. Use when adding monitors or cleaning up noisy pages.
Define a small set of type sizes on a ratio, with line height and measure tied to each, so text hierarchy is consistent without per-screen decisions. Use when setting typography, fixing inconsistent text, or starting a design system.
A one-page runbook that someone half-awake can follow. Use when a page or alert has no documented response yet.
Run a short exit interview that surfaces the real reason. Use after a cancel or silent churn.
Decide up front what would make you sunset a feature. Use when launching an experiment or a bet with unclear upside.
Cap prompt and output tokens before you tune quality. Use when an agent path is getting expensive or slow.
Define what the model must refuse and how it says no. Use when shipping a user-facing agent or tool-calling loop.
Draft a concrete rollback before you ship a risky change. Use when cutting over a migration, flipping a flag, or deploying something you cannot easily undo.
Review a landing hero for clarity and brand strength. Use when rewriting a marketing homepage.
Never capture without writing your own take. Use when saving an article, thread, or video into your library.
Capture what you tried on the bench before you forget. Use after soldering, flashing, or a failed bring-up.
Build a working model of an unfamiliar repo in one day. Use when joining a team or picking up a legacy service.
Walk a UI with the keyboard and fix tab order before visual polish. Use when shipping a form, modal, or new nav pattern.
Write the steps the next person can run at 3am — preconditions, exact commands, expected output, and when to stop — instead of a wiki that assumes you are in the room. Use when something will be done without you, before you go on leave, or after an incident you do not want twice.
Assume the project already failed, list the causes independently, and kill the cheap likely ones before you start — instead of brainstorming hopes. Use when you are about to launch, rewrite, migrate, or take any bet you cannot afford to only examine after it dies.
Get a new person to a first real shipped thing in five days — access on day one, a buddy, a done definition — instead of a wiki dump and a calendar of talks. Use when someone starts, when a teammate rotates in, or when onboarding still means "read Confluence."
Say the behaviour, the impact, and the ask — soon, and specific enough that tomorrow can be different — instead of a sandwich or a review-season surprise. Use when work missed the mark, when a pattern is repeating, or when praise is too vague to repeat.
Get better at one skill by drilling the part that fails, with fast feedback and a stop rule — instead of rereading notes and calling it practice. Use when a skill has plateaued, before a high-stakes performance, or when study time is not turning into ability.
Turn a book, talk, or domain into a handful of claims you can test this week — not a summary you will never reread. Use when finishing a dense source, entering a new field, or when notes are growing and understanding is not.
Unplug the mouse and walk the flow with Tab, visible focus, and a name for every control — then a screen reader on the unhappy paths. Use when a screen is "done," before a form ships, or when access is a backlog item with no method.
Watch five people who actually do the job try real tasks, and change the one thing that stalled them — instead of interviewing them about taste. Use when a flow is new, before a redesign ships, or when opinions about a screen will not converge.