ericrisco/rsc-harness / skills/dynamodb
dynamodb
VerifiedUse when modeling or operating a DynamoDB table: deriving partition/sort keys from access patterns, single-table vs table-per-entity, adding a GSI/LSI, on-demand vs provisioned capacity, or diagnosing hot-partition throttling. NOT relational schema/SQL/EXPLAIN (that is `postgresdb`), NOT aggregation-pipeline document modeling (that is `mongodb`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.9 KB |
| evals/README.md | markdown | 639 B |
| evals/cases.yaml | config | 3.3 KB |
| references/access-patterns.md | markdown | 5.0 KB |
| references/capacity-and-limits.md | markdown | 3.8 KB |
| scripts/verify.shexecutable | script | 4.8 KB |
evals/cases.yaml
View on GitHubskill: dynamodb
should_trigger:
- prompt: "Design a DynamoDB table for an e-commerce app — users, orders, and order items."
why: "Core access-pattern-first NoSQL modeling for the DynamoDB engine."
- prompt: "I need to look up a user by id AND by email in DynamoDB. How do I support both lookups?"
why: "Non-obvious — the answer is an inverted/sparse GSI, but the user never says 'GSI' or 'index'."
- prompt: "My DynamoDB writes are getting throttled even though I'm way under my provisioned capacity. Why?"
why: "Non-obvious — this is the per-partition 1000 WCU hot-partition ceiling, with no modeling vocabulary in the prompt."
- prompt: "Should I use on-demand or provisioned capacity for a workload that spikes hard at 9am and is quiet otherwise?"
why: "Capacity-mode decision the skill owns (on-demand is the post-Nov-2024 default for spiky traffic)."
- prompt: "Is single-table design actually worth it for my app, or should I use a table per entity?"
why: "The single-table-vs-table-per-entity call is squarely this skill's territory."
- prompt: "Diseña el modelo de DynamoDB para un chat: conversaciones y mensajes, con paginación."
why: "Spanish + access-pattern modeling (one-to-many) + the 1 MB page / LastEvaluatedKey pagination concern."
should_not_trigger:
- prompt: "Design a normalized Postgres schema with foreign keys for orders and customers, and add the right indexes."
route_to: postgresdb
why: "Relational engine — normalization, foreign keys, B-tree indexes are postgresdb's domain."
- prompt: "Model embedding-vs-referencing for my MongoDB documents and write the aggregation pipeline."
route_to: mongodb
why: "Document engine with an aggregation pipeline; not DynamoDB key/GSI modeling."
- prompt: "I want to store and query vector embeddings for semantic search."
route_to: vector-db
why: "Vector / semantic search, not key-value access-pattern modeling."
- prompt: "Set up my AWS account, IAM roles, and a VPC so I can start using AWS."
route_to: aws-essentials
why: "Account and infrastructure setup, not data modeling."
- prompt: "Cache these hot read results to take load off my database."
route_to: redis
why: "Caching layer is out of scope; DynamoDB owns the modeling, not the cache in front of it."
capability:
- scenario: >
A multi-tenant SaaS has entities Org, User, Project, and Task. It needs to: get all users in an org;
get a user's tasks newest-first; look up a user by email; and list all overdue tasks across an org.
Design the DynamoDB model and recommend a capacity mode.
must_include:
- "Enumerates the four access patterns BEFORE designing any keys"
- "Designs composite PK/SK with entity co-location under a single table and shows the encoding (e.g. PK=USER#id, SK=TASK#<iso>#id)"
- "Serves the email lookup via an inverted/sparse GSI and notes GSIs are eventually consistent (no read-your-own-write)"
- "Serves 'overdue tasks' via a sparse GSI (attribute written only on overdue items), not a Scan + FilterExpression"
- "Recommends on-demand as the default capacity mode while naming the ~40%-utilization threshold for switching to provisioned"
- "Flags the 400 KB item cap and the 1 MB Query page with LastEvaluatedKey pagination"
- "Does NOT propose normalized separate tables joined in application code"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |