LarrySequino
UserSkills I wrote for Claude. Published from a private working library.
Categories
Indexed Skills (18)
craft-review
Rigorous visual and UX design review for UI screens and flows. Use when the user asks to review a design, critique a screen, audit a UI, check spacing, alignment, hierarchy, typography, color, contrast or accessibility, asks whether something looks polished, off, or generically AI-generated, or shares a screenshot or Figma URL for feedback. Measures before it judges, and reports severity-ranked findings with numeric fixes. NOT for turning mocks into a decision page (use decision-artifact) and NOT for prose (use natural-writing).
skill-curator
Audit, evaluate, merge, and refresh a library of agent skills. Use when asked to review or clean up installed skills, check whether two skills collide on the same trigger, vet or compare third-party skills before installing, merge duplicates, harvest material from skill repos into an existing skill, or check a skill's upstream sources for updates. NOT for authoring a new skill from scratch (use skill-creator) and NOT for writing the subject-matter content inside one.
release-notes-draft
Turn the changes merged since the last tag into release notes grouped by reader impact, with breaking changes and upgrade steps listed first. Use when cutting a version and the notes still have to be written, or when a draft reads as a bare list of commits. NOT for writing the commit messages themselves (use commit-style instead).
natural-writing
Remove AI writing patterns from any prose a person will read, and keep them out of prose you write. EDIT AND AUDIT TRIGGERS: "deslop", "de-AI", "humanize", "make it sound human", "clean up this writing", "find the AI tells", "sounds robotic", "reads like a chatbot", "sounds like AI wrote it", "full of buzzwords". WRITE TRIGGERS: "write", "draft", "write up", "put together", "turn these notes into", or naming where it goes -- to send, to post, to publish, to share with someone. ARTIFACTS: any email, any letter, blog post, newsletter, social post, announcement, press release, any report, meeting notes, any proposal, README, docs, release notes, website or marketing copy, slide text, UI microcopy, artifact or published page. NOT TRIGGERED BY: "explain", "what is", "how do I", or any answer that stays in the conversation rather than going to a reader. NOT FOR: code, comments, commit messages, or interface typesetting such as quotes, dashes and ellipses as rendered.
api-docs-publish
Generate and publish reference documentation from an OpenAPI description: group operations the way a caller searches, add a request and reply example per operation, check that the examples still validate, and push the built site. Use when an endpoint moved and the published reference is stale. NOT for the marketing pages (use landing-copy instead).
csv-profiler
Profile a raw CSV before anyone builds on it: row and column counts, inferred types, null rates, duplicate keys, value ranges, and the columns that are secretly free text. Use when a fresh extract lands from a partner or a nightly job and nobody knows yet whether it is usable. NOT for loading it into a warehouse (use warehouse-loader for that).
design-tokens-sync
Read the design tokens out of a Figma library and write the values into the repository as CSS custom properties or a theme file, so the color and spacing in the app stop drifting from the source of truth. Use when a token changed upstream, when the palette no longer agrees with the design library, or when a rename has to land in the codebase. NOT for inventing new token names (use naming-conventions for that).
figma-handoff
Export measurements, color specs, and type specs from a Figma file, together with the design tokens behind each one, so a developer can implement the screen without opening the editor. Use when a designer marks a frame ready for handoff, or when a ticket links a Figma frame and carries no redlines. NOT for judging whether a screen is well designed (use visual-critique for that).
flaky-test-triage
Triage an intermittently failing test suite: parse recent continuous integration runs, rank tests by failure rate, separate real regressions from timing noise, and quarantine what is wasting the team's afternoon. Use when reruns pass and a red build has stopped meaning anything. NOT for authoring the tests themselves (use test-authoring for that).
k8s-rollout-check
Verify a Kubernetes rollout actually finished: replica readiness, restart loops, probe failures, pending pods, and the cluster events emitted while the deploy was running. Use right after shipping to a cluster, or when a deploy reports success and the service is still misbehaving. NOT for authoring the manifests (use helm-chart-author instead).
pdf-form-fill
Fill an existing PDF form: locate the AcroForm fields, enter the values into each field, flatten the result, and save a filled copy. Use when a blank government, HR, or insurance form lands and the answers have to be typed in. NOT for pdf-report-build, which composes a brand new document from a template; this one only writes into fields that already exist.
pdf-report-build
Compose a new PDF report from a template and a dataset: page layout, running headers, tables, charts, and page numbering, rendered so it prints correctly. Use when a recurring monthly or quarterly document has to be generated rather than typed by hand. NOT for pdf-form-fill, which enters answers into fields on a document that already exists; this one starts from an empty page.
spreadsheet-formulas
Repair and explain spreadsheet formulas: trace precedents, fix broken references, unpick nested conditionals, and rebuild a lookup that quietly matches the wrong entry. Use when a workbook produces a number nobody can account for, or when a sheet inherited from a colleague has to be trusted. NOT for charting the numbers (use dataviz instead).
sql-query-review
Review a SQL statement before it runs against production: missing indexes, accidental cross joins, unbounded scans, implicit casts that defeat an index, and how long it will hold locks. Use when a slow statement is posted for help, or when an engineer asks whether it is safe to run during business hours. NOT for planning schema migrations (use migration-planner instead).
alt-text-sweep
Walk every image in a documentation set and compose alt text that carries the same information the picture does, marking decorative art so it announces nothing at all. Use before an accessibility pass or a docs release. NOT for color contrast or focus order (use craft-review for those).
deploy-window-check
Decide whether a production deploy can go out right now: cross-reference the change freeze calendar, open incidents, and on-call coverage, then answer go or no-go with the reason attached. Use before pushing to production during a freeze or late in the week. NOT for performing the deploy itself (use release-runner instead).
schema-migrate-plan
Draft a two-phase database migration plan: expand, backfill, contract, with the rollback point named at each step and the read/write path stated for both halves. Use when a column has to change shape under live traffic. NOT for writing the application query changes themselves (use sql-query-tuning rather than this).
tidy-words
A short list of overused words to avoid in prose, with plainer replacements.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.