From 260d714740d8c9cdd66e241f5f97bd047b00088a Mon Sep 17 00:00:00 2001 From: Shayan Rais Date: Fri, 17 Apr 2026 06:29:02 +0500 Subject: [PATCH] rename thariq-17-mar-26 asset folder to thariq-26-3-17 Adopt YY-M-D naming scheme (year-month-date, month as numeric) for chronological sortability. Update image references in the skills-lessons post. Co-Authored-By: Claude --- .../1.png | Bin .../10.png | Bin .../11.png | Bin .../12.png | Bin .../13.png | Bin .../14.png | Bin .../15.png | Bin .../16.png | Bin .../17.png | Bin .../18.png | Bin .../19.png | Bin .../2.png | Bin .../20.png | Bin .../21.png | Bin .../22.png | Bin .../23.png | Bin .../24.png | Bin .../25.png | Bin .../26.png | Bin .../27.png | Bin .../3.png | Bin .../4.png | Bin .../5.png | Bin .../6.png | Bin .../7.png | Bin .../8.png | Bin .../9.png | Bin tips/claude-thariq-tips-17-mar-26.md | 54 +++++++++--------- 28 files changed, 27 insertions(+), 27 deletions(-) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/1.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/10.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/11.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/12.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/13.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/14.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/15.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/16.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/17.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/18.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/19.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/2.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/20.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/21.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/22.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/23.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/24.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/25.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/26.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/27.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/3.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/4.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/5.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/6.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/7.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/8.png (100%) rename tips/assets/{thariq-17-mar-26 => thariq-26-3-17}/9.png (100%) diff --git a/tips/assets/thariq-17-mar-26/1.png b/tips/assets/thariq-26-3-17/1.png similarity index 100% rename from tips/assets/thariq-17-mar-26/1.png rename to tips/assets/thariq-26-3-17/1.png diff --git a/tips/assets/thariq-17-mar-26/10.png b/tips/assets/thariq-26-3-17/10.png similarity index 100% rename from tips/assets/thariq-17-mar-26/10.png rename to tips/assets/thariq-26-3-17/10.png diff --git a/tips/assets/thariq-17-mar-26/11.png b/tips/assets/thariq-26-3-17/11.png similarity index 100% rename from tips/assets/thariq-17-mar-26/11.png rename to tips/assets/thariq-26-3-17/11.png diff --git a/tips/assets/thariq-17-mar-26/12.png b/tips/assets/thariq-26-3-17/12.png similarity index 100% rename from tips/assets/thariq-17-mar-26/12.png rename to tips/assets/thariq-26-3-17/12.png diff --git a/tips/assets/thariq-17-mar-26/13.png b/tips/assets/thariq-26-3-17/13.png similarity index 100% rename from tips/assets/thariq-17-mar-26/13.png rename to tips/assets/thariq-26-3-17/13.png diff --git a/tips/assets/thariq-17-mar-26/14.png b/tips/assets/thariq-26-3-17/14.png similarity index 100% rename from tips/assets/thariq-17-mar-26/14.png rename to tips/assets/thariq-26-3-17/14.png diff --git a/tips/assets/thariq-17-mar-26/15.png b/tips/assets/thariq-26-3-17/15.png similarity index 100% rename from tips/assets/thariq-17-mar-26/15.png rename to tips/assets/thariq-26-3-17/15.png diff --git a/tips/assets/thariq-17-mar-26/16.png b/tips/assets/thariq-26-3-17/16.png similarity index 100% rename from tips/assets/thariq-17-mar-26/16.png rename to tips/assets/thariq-26-3-17/16.png diff --git a/tips/assets/thariq-17-mar-26/17.png b/tips/assets/thariq-26-3-17/17.png similarity index 100% rename from tips/assets/thariq-17-mar-26/17.png rename to tips/assets/thariq-26-3-17/17.png diff --git a/tips/assets/thariq-17-mar-26/18.png b/tips/assets/thariq-26-3-17/18.png similarity index 100% rename from tips/assets/thariq-17-mar-26/18.png rename to tips/assets/thariq-26-3-17/18.png diff --git a/tips/assets/thariq-17-mar-26/19.png b/tips/assets/thariq-26-3-17/19.png similarity index 100% rename from tips/assets/thariq-17-mar-26/19.png rename to tips/assets/thariq-26-3-17/19.png diff --git a/tips/assets/thariq-17-mar-26/2.png b/tips/assets/thariq-26-3-17/2.png similarity index 100% rename from tips/assets/thariq-17-mar-26/2.png rename to tips/assets/thariq-26-3-17/2.png diff --git a/tips/assets/thariq-17-mar-26/20.png b/tips/assets/thariq-26-3-17/20.png similarity index 100% rename from tips/assets/thariq-17-mar-26/20.png rename to tips/assets/thariq-26-3-17/20.png diff --git a/tips/assets/thariq-17-mar-26/21.png b/tips/assets/thariq-26-3-17/21.png similarity index 100% rename from tips/assets/thariq-17-mar-26/21.png rename to tips/assets/thariq-26-3-17/21.png diff --git a/tips/assets/thariq-17-mar-26/22.png b/tips/assets/thariq-26-3-17/22.png similarity index 100% rename from tips/assets/thariq-17-mar-26/22.png rename to tips/assets/thariq-26-3-17/22.png diff --git a/tips/assets/thariq-17-mar-26/23.png b/tips/assets/thariq-26-3-17/23.png similarity index 100% rename from tips/assets/thariq-17-mar-26/23.png rename to tips/assets/thariq-26-3-17/23.png diff --git a/tips/assets/thariq-17-mar-26/24.png b/tips/assets/thariq-26-3-17/24.png similarity index 100% rename from tips/assets/thariq-17-mar-26/24.png rename to tips/assets/thariq-26-3-17/24.png diff --git a/tips/assets/thariq-17-mar-26/25.png b/tips/assets/thariq-26-3-17/25.png similarity index 100% rename from tips/assets/thariq-17-mar-26/25.png rename to tips/assets/thariq-26-3-17/25.png diff --git a/tips/assets/thariq-17-mar-26/26.png b/tips/assets/thariq-26-3-17/26.png similarity index 100% rename from tips/assets/thariq-17-mar-26/26.png rename to tips/assets/thariq-26-3-17/26.png diff --git a/tips/assets/thariq-17-mar-26/27.png b/tips/assets/thariq-26-3-17/27.png similarity index 100% rename from tips/assets/thariq-17-mar-26/27.png rename to tips/assets/thariq-26-3-17/27.png diff --git a/tips/assets/thariq-17-mar-26/3.png b/tips/assets/thariq-26-3-17/3.png similarity index 100% rename from tips/assets/thariq-17-mar-26/3.png rename to tips/assets/thariq-26-3-17/3.png diff --git a/tips/assets/thariq-17-mar-26/4.png b/tips/assets/thariq-26-3-17/4.png similarity index 100% rename from tips/assets/thariq-17-mar-26/4.png rename to tips/assets/thariq-26-3-17/4.png diff --git a/tips/assets/thariq-17-mar-26/5.png b/tips/assets/thariq-26-3-17/5.png similarity index 100% rename from tips/assets/thariq-17-mar-26/5.png rename to tips/assets/thariq-26-3-17/5.png diff --git a/tips/assets/thariq-17-mar-26/6.png b/tips/assets/thariq-26-3-17/6.png similarity index 100% rename from tips/assets/thariq-17-mar-26/6.png rename to tips/assets/thariq-26-3-17/6.png diff --git a/tips/assets/thariq-17-mar-26/7.png b/tips/assets/thariq-26-3-17/7.png similarity index 100% rename from tips/assets/thariq-17-mar-26/7.png rename to tips/assets/thariq-26-3-17/7.png diff --git a/tips/assets/thariq-17-mar-26/8.png b/tips/assets/thariq-26-3-17/8.png similarity index 100% rename from tips/assets/thariq-17-mar-26/8.png rename to tips/assets/thariq-26-3-17/8.png diff --git a/tips/assets/thariq-17-mar-26/9.png b/tips/assets/thariq-26-3-17/9.png similarity index 100% rename from tips/assets/thariq-17-mar-26/9.png rename to tips/assets/thariq-26-3-17/9.png diff --git a/tips/claude-thariq-tips-17-mar-26.md b/tips/claude-thariq-tips-17-mar-26.md index bc3f1ea..81d7375 100644 --- a/tips/claude-thariq-tips-17-mar-26.md +++ b/tips/claude-thariq-tips-17-mar-26.md @@ -15,7 +15,7 @@ A comprehensive guide on how Anthropic uses skills internally, shared by Thariq Skills have become one of the most used extension points in Claude Code. They're flexible, easy to make, and simple to distribute. But this flexibility also makes it hard to know what works best. Thariq shares the lessons learned from using skills extensively at Anthropic with hundreds of them in active use. -Thariq intro tweet +Thariq intro tweet --- @@ -23,7 +23,7 @@ Skills have become one of the most used extension points in Claude Code. They're A common misconception is that skills are "just markdown files", but the most interesting part is that they're **folders** that can include scripts, assets, data, etc. — things the agent can discover, explore, and manipulate. Skills also have a wide variety of configuration options including registering dynamic hooks. -What are Skills? +What are Skills? --- @@ -31,7 +31,7 @@ A common misconception is that skills are "just markdown files", but the most in After cataloging all of their skills, the team noticed they cluster into 9 recurring categories. The best skills fit cleanly into one; the more confusing ones straddle several. -Types of Skills grid +Types of Skills grid --- @@ -41,7 +41,7 @@ Skills that explain how to correctly use a library, CLI, or SDKs. These could be **Examples:** billing-lib, internal-platform-cli, frontend-design -Library & API Reference +Library & API Reference --- @@ -51,7 +51,7 @@ Skills that describe how to test or verify that your code is working. These are **Examples:** signup-flow-driver, checkout-verifier, tmux-cli-driver -Product Verification +Product Verification --- @@ -61,7 +61,7 @@ Skills that connect to your data and monitoring stacks. These might include libr **Examples:** funnel-query, cohort-compare, grafana -Data Fetching & Analysis +Data Fetching & Analysis --- @@ -71,7 +71,7 @@ Skills that automate repetitive workflows into one command. These are usually fa **Examples:** standup-post, create-\-ticket, weekly-recap -Business Process & Team Automation +Business Process & Team Automation --- @@ -81,7 +81,7 @@ Skills that generate framework boilerplate for a specific function in the codeba **Examples:** new-\-workflow, new-migration, create-app -Code Scaffolding & Templates +Code Scaffolding & Templates --- @@ -91,7 +91,7 @@ Skills that enforce code quality inside of your org and help review code. These **Examples:** adversarial-review, code-style, testing-practices -Code Quality & Review +Code Quality & Review --- @@ -101,7 +101,7 @@ Skills that help you fetch, push, and deploy code inside of your codebase. These **Examples:** babysit-pr, deploy-\, cherry-pick-prod -CI/CD & Deployment +CI/CD & Deployment --- @@ -111,7 +111,7 @@ Skills that take a symptom (such as a Slack thread, alert, or error signature), **Examples:** \-debugging, oncall-runner, log-correlator -Runbooks +Runbooks --- @@ -121,7 +121,7 @@ Skills that perform routine maintenance and operational procedures — some of w **Examples:** \-orphans, dependency-management, cost-investigation -Infrastructure Operations +Infrastructure Operations --- @@ -129,7 +129,7 @@ Skills that perform routine maintenance and operational procedures — some of w 9 best practices for writing effective skills, plus guidance on distribution and measurement. -Tips for Making Skills grid +Tips for Making Skills grid --- @@ -137,7 +137,7 @@ Skills that perform routine maintenance and operational procedures — some of w Claude Code knows a lot about your codebase, and Claude knows a lot about coding, including many default opinions. If you're publishing a skill that is primarily about knowledge, try to focus on information that pushes Claude out of its normal way of thinking. The frontend design skill is a great example — it was built by iterating with customers on improving Claude's design taste, avoiding classic patterns like the Inter font and purple gradients. -Don't State the Obvious +Don't State the Obvious --- @@ -145,7 +145,7 @@ Claude Code knows a lot about your codebase, and Claude knows a lot about coding The highest-signal content in any skill is the Gotchas section. These sections should be built up from common failure points that Claude runs into when using your skill. Ideally, you will update your skill over time to capture these gotchas. -Build a Gotchas Section +Build a Gotchas Section --- @@ -153,7 +153,7 @@ The highest-signal content in any skill is the Gotchas section. These sections s A skill is a folder, not just a markdown file. You should think of the entire file system as a form of context engineering and progressive disclosure. Tell Claude what files are in your skill, and it will read them at appropriate times. The simplest form is to point to other markdown files — e.g., split detailed function signatures and usage examples into `references/api.md`. You can have folders of references, scripts, examples, etc. -Progressive Disclosure +Progressive Disclosure --- @@ -161,7 +161,7 @@ A skill is a folder, not just a markdown file. You should think of the entire fi Claude will generally try to stick to your instructions, and because skills are so reusable you'll want to be careful of being too specific. Give Claude the information it needs, but give it the flexibility to adapt to the situation. Instead of prescriptive step-by-step instructions, give the goal and constraints. -Avoid Railroading Claude +Avoid Railroading Claude --- @@ -169,7 +169,7 @@ Claude will generally try to stick to your instructions, and because skills are Some skills may need to be set up with context from the user. A good pattern is to store this setup information in a `config.json` file in the skill directory. If the config is not set up, the agent can then ask the user for information. You can instruct Claude to use the AskUserQuestion tool for structured, multiple choice questions. -Think through the Setup +Think through the Setup --- @@ -177,7 +177,7 @@ Some skills may need to be set up with context from the user. A good pattern is When Claude Code starts a session, it builds a listing of every available skill with its description. This listing is what Claude scans to decide "is there a skill for this request?" Which means the description field is not a summary — it's a description of **when to trigger** this skill. Write it for the model. -Description = Trigger +Description = Trigger --- @@ -185,7 +185,7 @@ When Claude Code starts a session, it builds a listing of every available skill Some skills can include a form of memory by storing data within them. You could store data in anything as simple as an append-only text log file or JSON files, or as complicated as a SQLite database. Data stored in the skill directory may be deleted when you upgrade the skill, so use `${CLAUDE_PLUGIN_DATA}` as a stable folder per plugin to store data in. -Memory & Storing Data +Memory & Storing Data --- @@ -193,7 +193,7 @@ Some skills can include a form of memory by storing data within them. You could One of the most powerful tools you can give Claude is code. Giving Claude scripts and libraries lets Claude spend its turns on composition, deciding what to do next rather than reconstructing boilerplate. Claude can then generate scripts on the fly to compose this functionality for more advanced analysis. -Store Scripts & Generate Code +Store Scripts & Generate Code --- @@ -205,7 +205,7 @@ Skills can include hooks that are only activated when the skill is called, and l - `/careful` — blocks rm -rf, DROP TABLE, force-push, kubectl delete via PreToolUse matcher on Bash - `/freeze` — blocks any Edit/Write that's not in a specific directory -On Demand Hooks +On Demand Hooks --- @@ -217,7 +217,7 @@ Two ways to share skills with your team: Every skill that is checked in also adds a little bit to the context of the model. As you scale, an internal plugin marketplace allows you to distribute skills and let your team decide which ones to install. -Distributing Skills +Distributing Skills --- @@ -225,7 +225,7 @@ Every skill that is checked in also adds a little bit to the context of the mode There isn't a centralized team that decides which skills go into a marketplace. Instead, try and find the most useful skills organically. Upload to a sandbox folder in GitHub and point people to it in Slack or other forums. Once a skill has gotten traction (which is up to the skill owner to decide), they can put in a PR to move it into the marketplace. Curation before release is important to avoid redundant skills. -Managing a Marketplace +Managing a Marketplace --- @@ -233,7 +233,7 @@ There isn't a centralized team that decides which skills go into a marketplace. You may want to have skills that depend on each other. For example, a file upload skill that uploads a file, and a CSV generation skill that makes a CSV and uploads it. This sort of dependency management is not natively built into marketplaces or skills yet, but you can just reference other skills by name, and the model will invoke them if they are installed. -Composing Skills +Composing Skills --- @@ -241,7 +241,7 @@ You may want to have skills that depend on each other. For example, a file uploa To understand how a skill is doing, use a PreToolUse hook that lets you log skill usage within the company. This means you can find skills that are popular or are undertriggering compared to expectations. -Measuring Skills +Measuring Skills --- @@ -249,7 +249,7 @@ To understand how a skill is doing, use a PreToolUse hook that lets you log skil Skills are incredibly powerful, flexible tools for agents, but it's still early and we're all figuring out how to use them best. Think of this more as a grab bag of useful tips that we've seen work than a definitive guide. The best way to understand skills is to get started, experiment, and see what works for you. Most of ours began as a few lines and a single gotcha, and got better because people kept adding to them as Claude hit new edge cases. -Conclusion +Conclusion ---