- 📄 SKILL.md
vercel-doctor
Find ways to cut your Vercel bill. Run after making changes to catch cost-heavy patterns early in Next.js projects.
Find ways to cut your Vercel bill. Run after making changes to catch cost-heavy patterns early in Next.js projects.
Common analysis patterns for PolicyEngine research repositories (CRFB, newsletters, dashboards, impact studies). For population-level estimates (cost, poverty, distributional impacts), use the policyengine-microsimulation skill instead. --- # PolicyEngine analysis Patterns for creating policy impact analyses, dashboards, and research using PolicyEngine. **For population-level estimates** (budgetary cost, poverty impact, distributional analysis), use the **policyengine-microsimulation** skill instead. This skill covers analysis repo patterns, visualization, and household-level calculations. See `MICROSIMULATION_REFORM_GUIDE.md` for UK-specific microsimulation patterns. ## For Users ### What are Analysis Repositories?
Transform Chinese text into Chinglish (中式英語) — English that is heavily influenced by Chinese grammar, word order, and thought patterns, producing the characteristic "中式英文" style found on signs, menus, instructions, and everyday speech. Can also take English text and re-render it through a Chinese-thinking lens to produce Chinglish. Applies a 25-item checklist covering article errors, copula dropping, topic-comment structure, verb confusion, literal calques, tense flattening, and more. Useful for humor, creative writing, language education, or demonstrating L1 transfer patterns. Triggers on "/chinglish", "寫成中式英文", "翻成中式英語", "Chinglish化", "translate to chinglish", "make it chinglish", "chinglish this", "中式英文".
Evaluate a startup idea against real patterns from 101 founder interviews
Designs agent-native applications where agents are first-class citizens with full tool parity, atomic primitives, and explicit completion signals. Covers tool design, context injection, agent-to-UI communication, and mobile checkpoint/resume patterns. Use when architecting an agentic system, designing tool surfaces, building agent-aware UI, implementing context.md patterns, or asking "how do I make my app agent-native.
Analyze session replay patterns across experiment variants to understand user behavior differences. Use when the user wants to see how users interact with different experiment variants, identify usability issues, compare behavior patterns between control and test groups, or get qualitative insights to complement quantitative experiment results.
Build resilient, type-safe HTTP integrations with trembita using Result-based error handling, retries, and circuit breaker patterns. --- # Trembita Skill Use this repository as a practical reference for agents implementing HTTP clients with `trembita`. ## When to Use - Build TypeScript integrations for third-party REST APIs. - Add robust error handling without exception-driven control flow. - Implement retries, circuit breakers, and timeouts with minimal dependencies. - Write testable API code by injecting `fetchImpl`. ## Core Patterns 1. Initialize once with `createTrembita()` and handle init `Result`. 2. Use `client.request()` for parsed JSON body responses. 3. Use `client.client()` when you need HTTP metadata (`statusCode`, `body`). 4. Narrow failures by checking `result.error.kind`. 5. Add resilience via `createRetryingFetch` and `circuitBreaker` config. ## Canonical References - `README.md` - quick overview and install. - `QUICK_START.md` - shortest path to first success. - `LEARNING_GUIDE.md` - concepts and progressive examples. - `EXAMPLES.md` - production-style patterns. - `ARCHITECTURE.md` - request/error flow diagrams. ## Agent Guardrails - Prefer `Result` handling over `try/catch` for request outcomes. - Keep endpoint configuration explicit and validated. - Prefer `expectedCodes` to document acceptable HTTP outcomes. - Use `client.client()` for 404/202 branching by status code. - Inject `fetchImpl` in tests; avoid global fetch patching.
Analyze higher-level patterns in Claude Code usage. Outputs (a) graphic monthly/weekly digest with metaphors — aquarium of biomes (🐋🦈🐬🐟🦐🦠), archetypes (⚙️🔬🌐🛠📝🔍🏗💬), rhythm, stack palette, DORA radar (CFR + lead time + pushes), friction (compacts/pivots/subagents); (b) per-session parquet bundles for further analysis (biome, archetype, rhythm, growth, milestones, idle gaps, subagent pyramids, compact patterns, parallelism, burst classes, topics). Use when the user asks about weekly/monthly reports, session biomes, productivity profiles, "what kind of work was done", when a session became a whale, DORA metrics, or wants drill-down view of a specific session.
Create a new rsactor actor with proper structure and patterns.
v1.0.27 -- Detect and fix Go error handling antipatterns across a codebase. Use when auditing error handling, fixing double-handled errors, removing log-and-return patterns, cleaning up log-and-wrap helpers, or when the user asks to analyze error handling hygiene, find error handling violations, or ensure errors are handled exactly once. Covers detection patterns, classification of true vs false positives, fix strategies for interior vs boundary code, and verification steps.
Jest testing patterns, anti-patterns, and quality rules
Core conventions and patterns for this codebase
skill-sample/ ├─ SKILL.md ⭐ Required: skill entry doc (purpose / usage / examples / deps) ├─ manifest.sample.json ⭐ Recommended: machine-readable metadata (index / validation / autofill) ├─ LICENSE.sample ⭐ Recommended: license & scope (open source / restriction / commercial) ├─ scripts/ │ └─ example-run.py ✅ Runnable example script for quick verification ├─ assets/ │ ├─ example-formatting-guide.md 🧩 Output conventions: layout / structure / style │ └─ example-template.tex 🧩 Templates: quickly generate standardized output └─ references/ 🧩 Knowledge base: methods / guides / best practices ├─ example-ref-structure.md 🧩 Structure reference ├─ example-ref-analysis.md 🧩 Analysis reference └─ example-ref-visuals.md 🧩 Visual reference
More Agent Skills specs Anthropic docs: https://agentskills.io/home
├─ ⭐ Required: YAML Frontmatter (must be at top) │ ├─ ⭐ name : unique skill name, follow naming convention │ └─ ⭐ description : include trigger keywords for matching │ ├─ ✅ Optional: Frontmatter extension fields │ ├─ ✅ license : license identifier │ ├─ ✅ compatibility : runtime constraints when needed │ ├─ ✅ metadata : key-value fields (author/version/source_url...) │ └─ 🧩 allowed-tools : tool whitelist (experimental) │ └─ ✅ Recommended: Markdown body (progressive disclosure) ├─ ✅ Overview / Purpose ├─ ✅ When to use ├─ ✅ Step-by-step ├─ ✅ Inputs / Outputs ├─ ✅ Examples ├─ 🧩 Files & References ├─ 🧩 Edge cases ├─ 🧩 Troubleshooting └─ 🧩 Safety notes
Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.
We provide keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.
Quick Start:
Import/download skills (.zip/.skill), then place locally:
~/.claude/skills/ (Claude Code)
~/.codex/skills/ (Codex CLI)
One SKILL.md can be reused across tools.
Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.
A skill is a reusable capability package, usually including SKILL.md (purpose/IO/how-to) and optional scripts/templates/examples.
Think of it as a plugin playbook + resource bundle for AI assistants/toolchains.
Skills use progressive disclosure: load brief metadata first, load full docs only when needed, then execute by guidance.
This keeps agents lightweight while preserving enough context for complex tasks.
Use these three together:
Note: file size for all methods should be within 10MB.
Typical paths (may vary by local setup):
One SKILL.md can usually be reused across tools.
Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.
Example: retrieval + writing + automation scripts as one workflow.
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
Most common reasons:
We try to avoid that. Use ranking + comments to surface better skills: