Topic tag
skills
14 guides in the catalogue cover this topic.
- Nº 009 Capture the model's discipline Agents & Automation · Practitioner
Models get repriced, capped, and retired; their way of working can be kept. Extract the top model's discipline into skill files, routing tables, and planner-and-worker setups any model can run.
- Nº 010 Expertise you can install Agents & Automation · Broad
A skill file is career-long judgment packaged as instructions your agent can run. How to adopt someone's method, and why you scan it like untrusted input first.
- Nº 012 Every new repo starts with your lessons Agents & Automation · Broad
AI Firmware is a boot layer of kernel rules, installable skills, and committed memory that makes every new agent repo start senior instead of relearning old lessons.
- Nº 019 The design concept does the work Building with AI · Practitioner
The prompt and the reusable skill file behind the about page on this site, with the reason each part earns its place.
- Nº 045 One skills library for your whole team Agents & Automation · Practitioner
Skills built on one person's machine stay there, and the copies you send around go stale the moment anyone edits one. Put the team's skills in one GitHub repository, install it as a plugin, and every edit reaches every teammate's agent.
- Nº 050 Keep Claude automations working Agents & Automation · Practitioner
Turn a tested task into a reusable skill, choose where it runs, and catch failed work before it wastes more time.
- Nº 053 Compare AI agents on your own work Agents & Automation · Practitioner
Compare agents on one repeatable task, check the tools each can use, and keep your skills usable when you switch.
- Nº 054 Make skills improve after each run Agents & Automation · Practitioner
Use failed runs to repair skill descriptions, scripts, and checks. Test each change before keeping it, with Harness Firmware as a working example.
- Nº 055 Build a skill from an approved example Agents & Automation · Practitioner
Turn a result you already like into a reusable Codex skill. Define its task, decide where judgment belongs, and test it on fresh input.
- Nº 058 Set up Claude Code in seven steps Agents & Automation · Broad
Build a Claude setup in an order where each step builds on the one before: a working folder, shared pages, connected accounts, skills, scheduled runs, and a check before building new tools.
- Nº 061 Write smaller Claude skills that work Agents & Automation · Practitioner
Turn a repeated correction into a focused Claude Code skill. Choose when it runs, test its output, and remove instructions that add no value.
- Nº 063 Build an AI setup for one work task Agents & Automation · Practitioner
Choose one recurring task, give an existing agent your files and procedures, and check the result. Use Harness Firmware to keep the verified setup with your project.
- Nº 066 A practical guide to Claude's features Foundations · Broad
Choose where Claude should work, what it should make, which instructions to save, and when to use a goal or scheduled task.
- Nº 069 Why a few people get far more from AI Practice · Broad
Andrej Karpathy names three causes for the gap between casual and heavy AI use: the size of the problem, the kind of work, and access. Act on each, starting with one problem.