[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7D844AKTHR6CSFVZZDERTKJ":3,"skill-same:01M7D844AKTHR6CSFVZZDERTKJ":101},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7D844AKTHR6CSFVZZDERTKJ","senior-backend",null,"Designs and implements backend systems including REST APIs, microservices, database architectures, authentication flows, and security hardening. Use when the user asks to \"design REST APIs\", \"optimize database queries\", \"implement authentication\", \"build microservices\", \"review backend code\", \"set up GraphQL\", \"handle database migrations\", or \"load test APIs\". Covers Node.js\u002FExpress\u002FFastify development, PostgreSQL optimization, API security, and backend architecture patterns.","Mabbit143\u002FClaude-SKills","Mabbit143","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192994237?v=4","01M7D6X2W63K4T3N13CSVAKE3V","Mabbit Rountree","01M7D6X2WRPSZF8VMW9MW5ZP1X",0,"MIT","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-backend\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"senior-backend\"\ndescription: Designs and implements backend systems including REST APIs, microservices, database architectures, authentication flows, and security hardening. Use when the user asks to \"design REST APIs\", \"optimize database queries\", \"implement authentication\", \"build microservices\", \"review backend code\", \"set up GraphQL\", \"handle database migrations\", or \"load test APIs\". Covers Node.js\u002FExpress\u002FFastify development, PostgreSQL optimization, API security, and backend architecture patterns.\n---\n\n# Senior Backend Engineer\n\nBackend development patterns, API design, database optimization, and security practices.\n\n---\n\n## Quick Start\n\n```bash\n# Generate API routes from OpenAPI spec\npython scripts\u002Fapi_scaffolder.py openapi.yaml --framework express --output src\u002Froutes\u002F\n\n# Analyze database schema and generate migrations\npython scripts\u002Fdatabase_migration_tool.py --connection postgres:\u002F\u002Flocalhost\u002Fmydb --analyze\n\n# Load test an API endpoint\npython scripts\u002Fapi_load_tester.py https:\u002F\u002Fapi.example.com\u002Fusers --concurrency 50 --duration 30\n```\n\n---\n\n## Tools Overview\n\n### 1. API Scaffolder\n\nGenerates API route handlers, middleware, and OpenAPI specifications from schema definitions.\n\n**Input:** OpenAPI spec (YAML\u002FJSON) or database schema\n**Output:** Route handlers, validation middleware, TypeScript types\n\n**Usage:**\n```bash\n# Generate Express routes from OpenAPI spec\npython scripts\u002Fapi_scaffolder.py openapi.yaml --framework express --output src\u002Froutes\u002F\n# Output: Generated 12 route handlers, validation middleware, and TypeScript types\n\n# Generate from database schema\npython scripts\u002Fapi_scaffolder.py --from-db postgres:\u002F\u002Flocalhost\u002Fmydb --output src\u002Froutes\u002F\n\n# Generate OpenAPI spec from existing routes\npython scripts\u002Fapi_scaffolder.py src\u002Froutes\u002F --generate-spec --output openapi.yaml\n```\n\n**Supported Frameworks:**\n- Express.js (`--framework express`)\n- Fastify (`--framework fastify`)\n- Koa (`--framework koa`)\n\n---\n\n### 2. Database Migration Tool\n\nAnalyzes database schemas, detects changes, and generates migration files with rollback support.\n\n**Input:** Database connection string or schema files\n**Output:** Migration files, schema diff report, optimization suggestions\n\n**Usage:**\n```bash\n# Analyze current schema and suggest optimizations\npython scripts\u002Fdatabase_migration_tool.py --connection postgres:\u002F\u002Flocalhost\u002Fmydb --analyze\n# Output: Missing indexes, N+1 query risks, and suggested migration files\n\n# Generate migration from schema diff\npython scripts\u002Fdatabase_migration_tool.py --connection postgres:\u002F\u002Flocalhost\u002Fmydb \\\n  --compare schema\u002Fv2.sql --output migrations\u002F\n\n# Dry-run a migration\npython scripts\u002Fdatabase_migration_tool.py --connection postgres:\u002F\u002Flocalhost\u002Fmydb \\\n  --migrate migrations\u002F20240115_add_user_indexes.sql --dry-run\n```\n\n---\n\n### 3. API Load Tester\n\nPerforms HTTP load testing with configurable concurrency, measuring latency percentiles and throughput.\n\n**Input:** API endpoint URL and test configuration\n**Output:** Performance report with latency distribution, error rates, throughput metrics\n\n**Usage:**\n```bash\n# Basic load test\npython scripts\u002Fapi_load_tester.py https:\u002F\u002Fapi.example.com\u002Fusers --concurrency 50 --duration 30\n# Output: Throughput (req\u002Fsec), latency percentiles (P50\u002FP95\u002FP99), error counts, and scaling recommendations\n\n# Test with custom headers and body\npython scripts\u002Fapi_load_tester.py https:\u002F\u002Fapi.example.com\u002Forders \\\n  --method POST \\\n  --header \"Authorization: Bearer token123\" \\\n  --body '{\"product_id\": 1, \"quantity\": 2}' \\\n  --concurrency 100 \\\n  --duration 60\n\n# Compare two endpoints\npython scripts\u002Fapi_load_tester.py https:\u002F\u002Fapi.example.com\u002Fv1\u002Fusers https:\u002F\u002Fapi.example.com\u002Fv2\u002Fusers \\\n  --compare --concurrency 50 --duration 30\n```\n\n---\n\n## Backend Development Workflows\n\n### API Design Workflow\n\nUse when designing a new API or refactoring existing endpoints.\n\n**Step 1: Define resources and operations**\n```yaml\n# openapi.yaml\nopenapi: 3.0.3\ninfo:\n  title: User Service API\n  version: 1.0.0\npaths:\n  \u002Fusers:\n    get:\n      summary: List users\n      parameters:\n        - name: \"limit\"\n          in: query\n          schema:\n            type: integer\n            default: 20\n    post:\n      summary: Create user\n      requestBody:\n        required: true\n        content:\n          application\u002Fjson:\n            schema:\n              $ref: '#\u002Fcomponents\u002Fschemas\u002FCreateUser'\n```\n\n**Step 2: Generate route scaffolding**\n```bash\npython scripts\u002Fapi_scaffolder.py openapi.yaml --framework express --output src\u002Froutes\u002F\n```\n\n**Step 3: Implement business logic**\n```typescript\n\u002F\u002F src\u002Froutes\u002Fusers.ts (generated, then customized)\nexport const createUser = async (req: Request, res: Response) => {\n  const { email, name } = req.body;\n\n  \u002F\u002F Add business logic\n  const user = await userService.create({ email, name });\n\n  res.status(201).json(user);\n};\n```\n\n**Step 4: Add validation middleware**\n```bash\n# Validation is auto-generated from OpenAPI schema\n# src\u002Fmiddleware\u002Fvalidators.ts includes:\n# - Request body validation\n# - Query parameter validation\n# - Path parameter validation\n```\n\n**Step 5: Generate updated OpenAPI spec**\n```bash\npython scripts\u002Fapi_scaffolder.py src\u002Froutes\u002F --generate-spec --output openapi.yaml\n```\n\n---\n\n### Database Optimization Workflow\n\nUse when queries are slow or database performance needs improvement.\n\n**Step 1: Analyze current performance**\n```bash\npython scripts\u002Fdatabase_migration_tool.py --connection $DATABASE_URL --analyze\n```\n\n**Step 2: Identify slow queries**\n```sql\n-- Check query execution plans\nEXPLAIN ANALYZE SELECT * FROM orders\nWHERE user_id = 123\nORDER BY created_at DESC\nLIMIT 10;\n\n-- Look for: Seq Scan (bad), Index Scan (good)\n```\n\n**Step 3: Generate index migrations**\n```bash\npython scripts\u002Fdatabase_migration_tool.py --connection $DATABASE_URL \\\n  --suggest-indexes --output migrations\u002F\n```\n\n**Step 4: Test migration (dry-run)**\n```bash\npython scripts\u002Fdatabase_migration_tool.py --connection $DATABASE_URL \\\n  --migrate migrations\u002Fadd_indexes.sql --dry-run\n```\n\n**Step 5: Apply and verify**\n```bash\n# Apply migration\npython scripts\u002Fdatabase_migration_tool.py --connection $DATABASE_URL \\\n  --migrate migrations\u002Fadd_indexes.sql\n\n# Verify improvement\npython scripts\u002Fdatabase_migration_tool.py --connection $DATABASE_URL --analyze\n```\n\n---\n\n### Security Hardening Workflow\n\nUse when preparing an API for production or after a security review.\n\n**Step 1: Review authentication setup**\n```typescript\n\u002F\u002F Verify JWT configuration\nconst jwtConfig = {\n  secret: process.env.JWT_SECRET,  \u002F\u002F Must be from env, never hardcoded\n  expiresIn: '1h',                 \u002F\u002F Short-lived tokens\n  algorithm: 'RS256'               \u002F\u002F Prefer asymmetric\n};\n```\n\n**Step 2: Add rate limiting**\n```typescript\nimport rateLimit from 'express-rate-limit';\n\nconst apiLimiter = rateLimit({\n  windowMs: 15 * 60 * 1000,  \u002F\u002F 15 minutes\n  max: 100,                   \u002F\u002F 100 requests per window\n  standardHeaders: true,\n  legacyHeaders: false,\n});\n\napp.use('\u002Fapi\u002F', apiLimiter);\n```\n\n**Step 3: Validate all inputs**\n```typescript\nimport { z } from 'zod';\n\nconst CreateUserSchema = z.object({\n  email: z.string().email().max(255),\n  name: \"zstringmin1max100\"\n  age: z.number().int().positive().optional()\n});\n\n\u002F\u002F Use in route handler\nconst data = CreateUserSchema.parse(req.body);\n```\n\n**Step 4: Load test with attack patterns**\n```bash\n# Test rate limiting\npython scripts\u002Fapi_load_tester.py https:\u002F\u002Fapi.example.com\u002Flogin \\\n  --concurrency 200 --duration 10 --expect-rate-limit\n\n# Test input validation\npython scripts\u002Fapi_load_tester.py https:\u002F\u002Fapi.example.com\u002Fusers \\\n  --method POST \\\n  --body '{\"email\": \"not-an-email\"}' \\\n  --expect-status 400\n```\n\n**Step 5: Review security headers**\n```typescript\nimport helmet from 'helmet';\n\napp.use(helmet({\n  contentSecurityPolicy: true,\n  crossOriginEmbedderPolicy: true,\n  crossOriginOpenerPolicy: true,\n  crossOriginResourcePolicy: true,\n  hsts: { maxAge: 31536000, includeSubDomains: true },\n}));\n```\n\n---\n\n## Reference Documentation\n\n| File | Contains | Use When |\n|------|----------|----------|\n| `references\u002Fapi_design_patterns.md` | REST vs GraphQL, versioning, error handling, pagination | Designing new APIs |\n| `references\u002Fdatabase_optimization_guide.md` | Indexing strategies, query optimization, N+1 solutions | Fixing slow queries |\n| `references\u002Fbackend_security_practices.md` | OWASP Top 10, auth patterns, input validation | Security hardening |\n\n---\n\n## Common Patterns Quick Reference\n\n### REST API Response Format\n```json\n{\n  \"data\": { \"id\": 1, \"name\": \"John\" },\n  \"meta\": { \"requestId\": \"abc-123\" }\n}\n```\n\n### Error Response Format\n```json\n{\n  \"error\": {\n    \"code\": \"VALIDATION_ERROR\",\n    \"message\": \"Invalid email format\",\n    \"details\": [{ \"field\": \"email\", \"message\": \"must be valid email\" }]\n  },\n  \"meta\": { \"requestId\": \"abc-123\" }\n}\n```\n\n### HTTP Status Codes\n| Code | Use Case |\n|------|----------|\n| 200 | Success (GET, PUT, PATCH) |\n| 201 | Created (POST) |\n| 204 | No Content (DELETE) |\n| 400 | Validation error |\n| 401 | Authentication required |\n| 403 | Permission denied |\n| 404 | Resource not found |\n| 429 | Rate limit exceeded |\n| 500 | Internal server error |\n\n### Database Index Strategy\n```sql\n-- Single column (equality lookups)\nCREATE INDEX idx_users_email ON users(email);\n\n-- Composite (multi-column queries)\nCREATE INDEX idx_orders_user_status ON orders(user_id, status);\n\n-- Partial (filtered queries)\nCREATE INDEX idx_orders_active ON orders(created_at) WHERE status = 'active';\n\n-- Covering (avoid table lookup)\nCREATE INDEX idx_users_email_name ON users(email) INCLUDE (name);\n```\n\n---\n\n## Common Commands\n\n```bash\n# API Development\npython scripts\u002Fapi_scaffolder.py openapi.yaml --framework express\npython scripts\u002Fapi_scaffolder.py src\u002Froutes\u002F --generate-spec\n\n# Database Operations\npython scripts\u002Fdatabase_migration_tool.py --connection $DATABASE_URL --analyze\npython scripts\u002Fdatabase_migration_tool.py --connection $DATABASE_URL --migrate file.sql\n\n# Performance Testing\npython scripts\u002Fapi_load_tester.py https:\u002F\u002Fapi.example.com\u002Fendpoint --concurrency 50\npython scripts\u002Fapi_load_tester.py https:\u002F\u002Fapi.example.com\u002Fendpoint --compare baseline.json\n```\n\n---\n\n## Assumptions and Verifiable Success Criteria (Karpathy discipline)\n\nBefore this skill scaffolds, recommends a pattern, or modifies a schema, the following four assumptions MUST be surfaced. If any are unknown, the skill stops and walks the [Forcing-question library](#forcing-question-library-matt-pocock-grill) instead.\n\n1. **Read\u002Fwrite ratio + one-year p99 QPS** — drives DB, cache, queue, and partitioning choices. Kleppmann, *DDIA* (2017).\n2. **Tenancy model** — single-tenant, shared multi-tenant, isolated multi-tenant. Drives data-access pattern.\n3. **Data sensitivity tier** — public \u002F internal \u002F PII \u002F PHI \u002F PCI. Drives compliance floor.\n4. **SLO + named error-budget consumer** — Google SRE Workbook canon. No SLO = no reliability work prioritization.\n\n**Verifiable success criteria** (Karpathy #4) — every recommendation this skill emits must include:\n\n- Latency targets (p50, p95, p99 in ms)\n- Uptime \u002F SLO target\n- RPO + RTO\n\nIf any of those three is not stated, the recommendation is incomplete — return to Q7 of the forcing-question library.\n\nThe `scripts\u002Fbackend_decision_engine.py` tool encodes these checks: it refuses to recommend a profile without read\u002Fwrite ratio + QPS + tenancy + data sensitivity + pattern preference.\n\n---\n\n## Customization profiles\n\nFour built-in profiles in `profiles\u002F` calibrate every recommendation:\n\n| Profile | When to pick | Pattern | Latency floor (p99) |\n|---|---|---|---|\n| `node-express` | TS team, \u003C 15 eng, customer-facing SaaS | Modular monolith on Postgres | 600ms |\n| `fastapi-python` | Python team, \u003C 20 eng, ML-adjacent | Modular monolith on Postgres (async) | 500ms |\n| `django-monolith` | Content-heavy CRUD + admin, \u003C 25 eng | Modular monolith on Postgres | 800ms |\n| `go-or-rust-microservice` | Extracted service, ≥ 30 eng, platform team, QPS ≥ 1000 | Extracted service | 200ms |\n\nPick a profile via:\n\n```bash\npython scripts\u002Fbackend_decision_engine.py \\\n  --team-size 8 --qps-p99 50 --read-write-ratio 20 \\\n  --tenancy shared-multi-tenant --data-sensitivity pii \\\n  --pattern modular-monolith --language-preference typescript\n```\n\nThe tool returns the best-fit profile, runner-up tradeoff (if within 15%), stack picks, anti-patterns, named approvers, and SLO floor. **This tool never auto-approves.**\n\nTo add a custom profile: copy `profiles\u002Fnode-express.json` to `profiles\u002F\u003Cyour-org>.json` and adjust `constraints` + `success_thresholds` + `named_approver_chain`.\n\n---\n\n## Composition map\n\nThis skill does NOT reimplement scope owned by the POWERFUL-tier specialists. It forks into them. See `references\u002Fcomposition_map.md` for the full routing table. Key forks:\n\n| Concern | Fork into |\n|---|---|\n| API contract \u002F breaking-change risk | `engineering\u002Fskills\u002Fapi-design-reviewer\u002F` |\n| Schema design + ERD + indexing | `engineering\u002Fskills\u002Fdatabase-designer\u002F` |\n| Zero-downtime schema migration | `engineering\u002Fskills\u002Fmigration-architect\u002F` |\n| SLO + SLI + error-budget | `engineering\u002Fslo-architect\u002F` |\n| Observability \u002F golden signals | `engineering\u002Fskills\u002Fobservability-designer\u002F` |\n| CI\u002FCD pipeline | `engineering\u002Fskills\u002Fci-cd-pipeline-builder\u002F` |\n| Security \u002F threat model | `engineering-team\u002Fskills\u002Fsenior-security\u002F`, `adversarial-reviewer` |\n| Compliance evidence (HIPAA \u002F ISO 27001) | `ra-qm-team\u002F` |\n| Pre-commit Karpathy review | `engineering\u002Fkarpathy-coder\u002F` |\n| Pre-flight architecture grill | `engineering\u002Fgrill-me\u002F` |\n\nThe `cs-backend-engineer` agent orchestrates these forks via `context: fork`. Invoke it from another agent with `Agent({subagent_type: \"cs-backend-engineer\", prompt: \"...\"})` or via `\u002Fcs:backend-review \u003Cyour problem>`.\n\n---\n\n## Forcing-question library (Matt Pocock grill)\n\nBefore locking any backend decision, walk the seven forcing questions in `references\u002Fforcing_questions.md`. Discipline:\n\n1. One question per turn. No bundling.\n2. Always recommend the answer with cited canon.\n3. Track answers in `\u002Ftmp\u002Fbackend-grill-\u003Cdate>.md`.\n4. If a kill criterion trips, stop. Don't scaffold around an unresolved gap.\n5. After Q7, run `backend_decision_engine.py` with the seven answers.\n\nSummary:\n\n1. Read\u002Fwrite ratio + p99 QPS forecast?\n2. Tenancy model — single \u002F shared \u002F isolated?\n3. Sync \u002F async \u002F event-driven — default + exceptions?\n4. Data sensitivity tier — PII \u002F PHI \u002F PCI?\n5. Monolith \u002F modular monolith \u002F microservices — team-size justification?\n6. RPO + RTO?\n7. SLO + named error-budget consumer?\n\n---\n\n## Invocation from other agents and skills\n\nThree surfaces:\n\n1. **Slash command:** `\u002Fcs:backend-review \u003Cprompt>` — full grill + decision engine + composition routing.\n2. **Agent subagent:** `Agent({subagent_type: \"cs-backend-engineer\", prompt: \"...\"})` — forks context, returns ≤ 200-word digest.\n3. **Direct tool call:** `python scripts\u002Fbackend_decision_engine.py ...` — deterministic profile match when inputs are known.\n\nSee `agents\u002Fengineering\u002Fcs-backend-engineer.md` for the full invocation contract.\n","# Senior Backend Engineer\n\nBackend development patterns, API design, database optimization, and security practices.\n\n---\n\n## Quick Start\n\n```bash\n# Generate API routes from OpenAPI spec\npython scripts\u002Fapi_scaffolder.py openapi.yaml --framework express --output src\u002Froutes\u002F\n\n# Analyze database schema and generate migrations\npython scripts\u002Fdatabase_migration_tool.py --connection postgres:\u002F\u002Flocalhost\u002Fmydb --analyze\n\n# Load test an API endpoint\npython scripts\u002Fapi_load_tester.py https:\u002F\u002Fapi.example.com\u002Fusers --concurrency 50 --duration 30\n```\n\n---\n\n## Tools Overview\n\n### 1. API Scaffolder\n\nGenerates API route handlers, middleware, and OpenAPI specifications from schema definitions.\n\n**Input:** OpenAPI spec (YAML\u002FJSON) or database schema\n**Output:** Route handlers, validation middleware, TypeScript types\n\n**Usage:**\n```bash\n# Generate Express routes from OpenAPI spec\npython scripts\u002Fapi_scaffolder.py openapi.yaml --framework express --output src\u002Froutes\u002F\n# Output: Generated 12 route handlers, validation middleware, and TypeScript types\n\n# Generate from database schema\npython scripts\u002Fapi_scaffolder.py --from-db postgres:\u002F\u002Flocalhost\u002Fmydb --output src\u002Froutes\u002F\n\n# Generate OpenAPI spec from existing routes\npython scripts\u002Fapi_scaffolder.py src\u002Froutes\u002F --generate-spec --output openapi.yaml\n```\n\n**Supported Frameworks:**\n- Express.js (`--framework express`)\n- Fastify (`--framework fastify`)\n- Koa (`--framework koa`)\n\n---\n\n### 2. Database Migration Tool\n\nAnalyzes database schemas, detects changes, and generates migration files with rollback support.\n\n**Input:** Database connection string or schema files\n**Output:** Migration files, schema diff report, optimization suggestions\n\n**Usage:**\n```bash\n# Analyze current schema and suggest optimizations\npython scripts\u002Fdatabase_migration_tool.py --connection postgres:\u002F\u002Flocalhost\u002Fmydb --analyze\n# Output: Missing indexes, N+1 query risks, and suggested migration files\n\n# Generate migration from schema diff\npython scripts\u002Fdatabase_migration_tool.py --connection postgres:\u002F\u002Flocalhost\u002Fmydb \\\n  --compare schema\u002Fv2.sql --output migrations\u002F\n\n# Dry-run a migration\npython scripts\u002Fdatabase_migration_tool.py --connection postgres:\u002F\u002Flocalhost\u002Fmydb \\\n  --migrate migrations\u002F20240115_add_user_indexes.sql --dry-run\n```\n\n---\n\n### 3. API Load Tester\n\nPerforms HTTP load testing with configurable concurrency, measuring latency percentiles and throughput.\n\n**Input:** API endpoint URL and test configuration\n**Output:** Performance report with latency distribution, error rates, throughput metrics\n\n**Usage:**\n```bash\n# Basic load test\npython scripts\u002Fapi_load_tester.py https:\u002F\u002Fapi.example.com\u002Fusers --concurrency 50 --duration 30\n# Output: Throughput (req\u002Fsec), latency percentiles (P50\u002FP95\u002FP99), error counts, and scaling recommendations\n\n# Test with custom headers and body\npython scripts\u002Fapi_load_tester.py https:\u002F\u002Fapi.example.com\u002Forders \\\n  --method POST \\\n  --header \"Authorization: Bearer token123\" \\\n  --body '{\"product_id\": 1, \"quantity\": 2}' \\\n  --concurrency 100 \\\n  --duration 60\n\n# Compare two endpoints\npython scripts\u002Fapi_load_tester.py https:\u002F\u002Fapi.example.com\u002Fv1\u002Fusers https:\u002F\u002Fapi.example.com\u002Fv2\u002Fusers \\\n  --compare --concurrency 50 --duration 30\n```\n\n---\n\n## Backend Development Workflows\n\n### API Design Workflow\n\nUse when designing a new API or refactoring existing endpoints.\n\n**Step 1: Define resources and operations**\n```yaml\n# openapi.yaml\nopenapi: 3.0.3\ninfo:\n  title: User Service API\n  version: 1.0.0\npaths:\n  \u002Fusers:\n    get:\n      summary: List users\n      parameters:\n        - name: \"limit\"\n          in: query\n          schema:\n            type: integer\n            default: 20\n    post:\n      summary: Create user\n      requestBody:\n        required: true\n        content:\n          application\u002Fjson:\n            schema:\n              $ref: '#\u002Fcomponents\u002Fschemas\u002FCreateUser'\n```\n\n**Step 2: Generate route scaffolding**\n```bash\npython scripts\u002Fapi_scaffolder.py openapi.yaml --framework express --output src\u002Froutes\u002F\n```\n\n**Step 3: Implement business logic**\n```typescript\n\u002F\u002F src\u002Froutes\u002Fusers.ts (generated, then customized)\nexport const createUser = async (req: Request, res: Response) => {\n  const { email, name } = req.body;\n\n  \u002F\u002F Add business logic\n  const user = await userService.create({ email, name });\n\n  res.status(201).json(user);\n};\n```\n\n**Step 4: Add validation middleware**\n```bash\n# Validation is auto-generated from OpenAPI schema\n# src\u002Fmiddleware\u002Fvalidators.ts includes:\n# - Request body validation\n# - Query parameter validation\n# - Path parameter validation\n```\n\n**Step 5: Generate updated OpenAPI spec**\n```bash\npython scripts\u002Fapi_scaffolder.py src\u002Froutes\u002F --generate-spec --output openapi.yaml\n```\n\n---\n\n### Database Optimization Workflow\n\nUse when queries are slow or database performance needs improvement.\n\n**Step 1: Analyze current performance**\n```bash\npython scripts\u002Fdatabase_migration_tool.py --connection $DATABASE_URL --analyze\n```\n\n**Step 2: Identify slow queries**\n```sql\n-- Check query execution plans\nEXPLAIN ANALYZE SELECT * FROM orders\nWHERE user_id = 123\nORDER BY created_at DESC\nLIMIT 10;\n\n-- Look for: Seq Scan (bad), Index Scan (good)\n```\n\n**Step 3: Generate index migrations**\n```bash\npython scripts\u002Fdatabase_migration_tool.py --connection $DATABASE_URL \\\n  --suggest-indexes --output migrations\u002F\n```\n\n**Step 4: Test migration (dry-run)**\n```bash\npython scripts\u002Fdatabase_migration_tool.py --connection $DATABASE_URL \\\n  --migrate migrations\u002Fadd_indexes.sql --dry-run\n```\n\n**Step 5: Apply and verify**\n```bash\n# Apply migration\npython scripts\u002Fdatabase_migration_tool.py --connection $DATABASE_URL \\\n  --migrate migrations\u002Fadd_indexes.sql\n\n# Verify improvement\npython scripts\u002Fdatabase_migration_tool.py --connection $DATABASE_URL --analyze\n```\n\n---\n\n### Security Hardening Workflow\n\nUse when preparing an API for production or after a security review.\n\n**Step 1: Review authentication setup**\n```typescript\n\u002F\u002F Verify JWT configuration\nconst jwtConfig = {\n  secret: process.env.JWT_SECRET,  \u002F\u002F Must be from env, never hardcoded\n  expiresIn: '1h',                 \u002F\u002F Short-lived tokens\n  algorithm: 'RS256'               \u002F\u002F Prefer asymmetric\n};\n```\n\n**Step 2: Add rate limiting**\n```typescript\nimport rateLimit from 'express-rate-limit';\n\nconst apiLimiter = rateLimit({\n  windowMs: 15 * 60 * 1000,  \u002F\u002F 15 minutes\n  max: 100,                   \u002F\u002F 100 requests per window\n  standardHeaders: true,\n  legacyHeaders: false,\n});\n\napp.use('\u002Fapi\u002F', apiLimiter);\n```\n\n**Step 3: Validate all inputs**\n```typescript\nimport { z } from 'zod';\n\nconst CreateUserSchema = z.object({\n  email: z.string().email().max(255),\n  name: \"zstringmin1max100\"\n  age: z.number().int().positive().optional()\n});\n\n\u002F\u002F Use in route handler\nconst data = CreateUserSchema.parse(req.body);\n```\n\n**Step 4: Load test with attack patterns**\n```bash\n# Test rate limiting\npython scripts\u002Fapi_load_tester.py https:\u002F\u002Fapi.example.com\u002Flogin \\\n  --concurrency 200 --duration 10 --expect-rate-limit\n\n# Test input validation\npython scripts\u002Fapi_load_tester.py https:\u002F\u002Fapi.example.com\u002Fusers \\\n  --method POST \\\n  --body '{\"email\": \"not-an-email\"}' \\\n  --expect-status 400\n```\n\n**Step 5: Review security headers**\n```typescript\nimport helmet from 'helmet';\n\napp.use(helmet({\n  contentSecurityPolicy: true,\n  crossOriginEmbedderPolicy: true,\n  crossOriginOpenerPolicy: true,\n  crossOriginResourcePolicy: true,\n  hsts: { maxAge: 31536000, includeSubDomains: true },\n}));\n```\n\n---\n\n## Reference Documentation\n\n| File | Contains | Use When |\n|------|----------|----------|\n| `references\u002Fapi_design_patterns.md` | REST vs GraphQL, versioning, error handling, pagination | Designing new APIs |\n| `references\u002Fdatabase_optimization_guide.md` | Indexing strategies, query optimization, N+1 solutions | Fixing slow queries |\n| `references\u002Fbackend_security_practices.md` | OWASP Top 10, auth patterns, input validation | Security hardening |\n\n---\n\n## Common Patterns Quick Reference\n\n### REST API Response Format\n```json\n{\n  \"data\": { \"id\": 1, \"name\": \"John\" },\n  \"meta\": { \"requestId\": \"abc-123\" }\n}\n```\n\n### Error Response Format\n```json\n{\n  \"error\": {\n    \"code\": \"VALIDATION_ERROR\",\n    \"message\": \"Invalid email format\",\n    \"details\": [{ \"field\": \"email\", \"message\": \"must be valid email\" }]\n  },\n  \"meta\": { \"requestId\": \"abc-123\" }\n}\n```\n\n### HTTP Status Codes\n| Code | Use Case |\n|------|----------|\n| 200 | Success (GET, PUT, PATCH) |\n| 201 | Created (POST) |\n| 204 | No Content (DELETE) |\n| 400 | Validation error |\n| 401 | Authentication required |\n| 403 | Permission denied |\n| 404 | Resource not found |\n| 429 | Rate limit exceeded |\n| 500 | Internal server error |\n\n### Database Index Strategy\n```sql\n-- Single column (equality lookups)\nCREATE INDEX idx_users_email ON users(email);\n\n-- Composite (multi-column queries)\nCREATE INDEX idx_orders_user_status ON orders(user_id, status);\n\n-- Partial (filtered queries)\nCREATE INDEX idx_orders_active ON orders(created_at) WHERE status = 'active';\n\n-- Covering (avoid table lookup)\nCREATE INDEX idx_users_email_name ON users(email) INCLUDE (name);\n```\n\n---\n\n## Common Commands\n\n```bash\n# API Development\npython scripts\u002Fapi_scaffolder.py openapi.yaml --framework express\npython scripts\u002Fapi_scaffolder.py src\u002Froutes\u002F --generate-spec\n\n# Database Operations\npython scripts\u002Fdatabase_migration_tool.py --connection $DATABASE_URL --analyze\npython scripts\u002Fdatabase_migration_tool.py --connection $DATABASE_URL --migrate file.sql\n\n# Performance Testing\npython scripts\u002Fapi_load_tester.py https:\u002F\u002Fapi.example.com\u002Fendpoint --concurrency 50\npython scripts\u002Fapi_load_tester.py https:\u002F\u002Fapi.example.com\u002Fendpoint --compare baseline.json\n```\n\n---\n\n## Assumptions and Verifiable Success Criteria (Karpathy discipline)\n\nBefore this skill scaffolds, recommends a pattern, or modifies a schema, the following four assumptions MUST be surfaced. If any are unknown, the skill stops and walks the [Forcing-question library](#forcing-question-library-matt-pocock-grill) instead.\n\n1. **Read\u002Fwrite ratio + one-year p99 QPS** — drives DB, cache, queue, and partitioning choices. Kleppmann, *DDIA* (2017).\n2. **Tenancy model** — single-tenant, shared multi-tenant, isolated multi-tenant. Drives data-access pattern.\n3. **Data sensitivity tier** — public \u002F internal \u002F PII \u002F PHI \u002F PCI. Drives compliance floor.\n4. **SLO + named error-budget consumer** — Google SRE Workbook canon. No SLO = no reliability work prioritization.\n\n**Verifiable success criteria** (Karpathy #4) — every recommendation this skill emits must include:\n\n- Latency targets (p50, p95, p99 in ms)\n- Uptime \u002F SLO target\n- RPO + RTO\n\nIf any of those three is not stated, the recommendation is incomplete — return to Q7 of the forcing-question library.\n\nThe `scripts\u002Fbackend_decision_engine.py` tool encodes these checks: it refuses to recommend a profile without read\u002Fwrite ratio + QPS + tenancy + data sensitivity + pattern preference.\n\n---\n\n## Customization profiles\n\nFour built-in profiles in `profiles\u002F` calibrate every recommendation:\n\n| Profile | When to pick | Pattern | Latency floor (p99) |\n|---|---|---|---|\n| `node-express` | TS team, \u003C 15 eng, customer-facing SaaS | Modular monolith on Postgres | 600ms |\n| `fastapi-python` | Python team, \u003C 20 eng, ML-adjacent | Modular monolith on Postgres (async) | 500ms |\n| `django-monolith` | Content-heavy CRUD + admin, \u003C 25 eng | Modular monolith on Postgres | 800ms |\n| `go-or-rust-microservice` | Extracted service, ≥ 30 eng, platform team, QPS ≥ 1000 | Extracted service | 200ms |\n\nPick a profile via:\n\n```bash\npython scripts\u002Fbackend_decision_engine.py \\\n  --team-size 8 --qps-p99 50 --read-write-ratio 20 \\\n  --tenancy shared-multi-tenant --data-sensitivity pii \\\n  --pattern modular-monolith --language-preference typescript\n```\n\nThe tool returns the best-fit profile, runner-up tradeoff (if within 15%), stack picks, anti-patterns, named approvers, and SLO floor. **This tool never auto-approves.**\n\nTo add a custom profile: copy `profiles\u002Fnode-express.json` to `profiles\u002F\u003Cyour-org>.json` and adjust `constraints` + `success_thresholds` + `named_approver_chain`.\n\n---\n\n## Composition map\n\nThis skill does NOT reimplement scope owned by the POWERFUL-tier specialists. It forks into them. See `references\u002Fcomposition_map.md` for the full routing table. Key forks:\n\n| Concern | Fork into |\n|---|---|\n| API contract \u002F breaking-change risk | `engineering\u002Fskills\u002Fapi-design-reviewer\u002F` |\n| Schema design + ERD + indexing | `engineering\u002Fskills\u002Fdatabase-designer\u002F` |\n| Zero-downtime schema migration | `engineering\u002Fskills\u002Fmigration-architect\u002F` |\n| SLO + SLI + error-budget | `engineering\u002Fslo-architect\u002F` |\n| Observability \u002F golden signals | `engineering\u002Fskills\u002Fobservability-designer\u002F` |\n| CI\u002FCD pipeline | `engineering\u002Fskills\u002Fci-cd-pipeline-builder\u002F` |\n| Security \u002F threat model | `engineering-team\u002Fskills\u002Fsenior-security\u002F`, `adversarial-reviewer` |\n| Compliance evidence (HIPAA \u002F ISO 27001) | `ra-qm-team\u002F` |\n| Pre-commit Karpathy review | `engineering\u002Fkarpathy-coder\u002F` |\n| Pre-flight architecture grill | `engineering\u002Fgrill-me\u002F` |\n\nThe `cs-backend-engineer` agent orchestrates these forks via `context: fork`. Invoke it from another agent with `Agent({subagent_type: \"cs-backend-engineer\", prompt: \"...\"})` or via `\u002Fcs:backend-review \u003Cyour problem>`.\n\n---\n\n## Forcing-question library (Matt Pocock grill)\n\nBefore locking any backend decision, walk the seven forcing questions in `references\u002Fforcing_questions.md`. Discipline:\n\n1. One question per turn. No bundling.\n2. Always recommend the answer with cited canon.\n3. Track answers in `\u002Ftmp\u002Fbackend-grill-\u003Cdate>.md`.\n4. If a kill criterion trips, stop. Don't scaffold around an unresolved gap.\n5. After Q7, run `backend_decision_engine.py` with the seven answers.\n\nSummary:\n\n1. Read\u002Fwrite ratio + p99 QPS forecast?\n2. Tenancy model — single \u002F shared \u002F isolated?\n3. Sync \u002F async \u002F event-driven — default + exceptions?\n4. Data sensitivity tier — PII \u002F PHI \u002F PCI?\n5. Monolith \u002F modular monolith \u002F microservices — team-size justification?\n6. RPO + RTO?\n7. SLO + named error-budget consumer?\n\n---\n\n## Invocation from other agents and skills\n\nThree surfaces:\n\n1. **Slash command:** `\u002Fcs:backend-review \u003Cprompt>` — full grill + decision engine + composition routing.\n2. **Agent subagent:** `Agent({subagent_type: \"cs-backend-engineer\", prompt: \"...\"})` — forks context, returns ≤ 200-word digest.\n3. **Direct tool call:** `python scripts\u002Fbackend_decision_engine.py ...` — deterministic profile match when inputs are known.\n\nSee `agents\u002Fengineering\u002Fcs-backend-engineer.md` for the full invocation contract.\n",{"name":5,"description":7},"claude\u002Fregistry-repo-7lRiv","44e1a5b2d387b250bcd0794f7eb5e1228223d1e2","engineering-team\u002Fskills\u002Fsenior-backend","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills","https:\u002F\u002Fgithub.com\u002FMabbit143","I’m edgy and fun, probably too serious, but I love an adventure.","2026-09-22 07:56:32",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Mabbit143\u002FClaude-SKills --skill senior-backend",{"tool":37,"command":38},"bunx","bunx skills add Mabbit143\u002FClaude-SKills --skill senior-backend",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Mabbit143\u002FClaude-SKills --skill senior-backend","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-backend\u002FSKILL.md",true,[45,51,55,59,63,67,71,75,79,83,89,93,97],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"profiles\u002Fdjango-monolith.json","REFERENCE","参考文档",2334,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-backend\u002Fprofiles\u002Fdjango-monolith.json",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"profiles\u002Ffastapi-python.json",2515,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-backend\u002Fprofiles\u002Ffastapi-python.json",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"profiles\u002Fgo-or-rust-microservice.json",2995,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-backend\u002Fprofiles\u002Fgo-or-rust-microservice.json",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"profiles\u002Fnode-express.json",2523,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-backend\u002Fprofiles\u002Fnode-express.json",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fapi_design_patterns.md",13639,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-backend\u002Freferences\u002Fapi_design_patterns.md",{"path":68,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fbackend_security_practices.md",25480,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-backend\u002Freferences\u002Fbackend_security_practices.md",{"path":72,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fcomposition_map.md",5404,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-backend\u002Freferences\u002Fcomposition_map.md",{"path":76,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fdatabase_optimization_guide.md",13949,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-backend\u002Freferences\u002Fdatabase_optimization_guide.md",{"path":80,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fforcing_questions.md",8594,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-backend\u002Freferences\u002Fforcing_questions.md",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fapi_load_tester.py","SCRIPT","脚本",19800,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-backend\u002Fscripts\u002Fapi_load_tester.py",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Fapi_scaffolder.py",21442,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-backend\u002Fscripts\u002Fapi_scaffolder.py",{"path":94,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Fbackend_decision_engine.py",15663,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-backend\u002Fscripts\u002Fbackend_decision_engine.py",{"path":98,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":99,"sourceHtmlUrl":100},"scripts\u002Fdatabase_migration_tool.py",32200,"https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fengineering-team\u002Fskills\u002Fsenior-backend\u002Fscripts\u002Fdatabase_migration_tool.py",[102,109,116,123,130,137],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7D99ZA4F916M5CM3K2EQFE8","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M7D99ND4B38EG1BYQX722F5D","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers — \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":19},"01M7D999VS936SV9TX940A98AQ","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":19},"01M7D98XBECS6368GEJNG8C1Z1","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":19},"01M7D98N2R7CA7RM00PNP4VV6C","notebooklm","Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM — 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":19},"01M7D98B1SCTS4RAWZFCF9QJ5M","litreview","Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list — that's a plain Consensus search.","https:\u002F\u002Fgithub.com\u002FMabbit143\u002FClaude-SKills\u002Fblob\u002Fclaude\u002Fregistry-repo-7lRiv\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]