100 skills · sorted by relevance
Rehearse Convex schema changes on a deployment seeded with a production snapshot. Populate existing records, verify data and behavior, then repeat the proven sequence in production with explicit approval, keeping the snapshot available for rollback.
Update the data structure of a deployed Convex app through staged changes. Using @convex-dev/migrations, the skill fills or transforms existing records, checks validity and record counts, and makes new fields required after migration finishes.
Plan changes to Convex data structures while an app keeps running. The skill guides staged deployments, updates to existing records, and verification for required fields, type changes, and table restructuring using @convex-dev/migrations.
Build in-game changelogs that connect release notes and displayed versions to successful production deployments. Reconstruct supported history, integrate menu navigation and accessible controls, and verify version consistency and behavior on desktop and mobile.
Use Quicknode to connect applications to blockchains, retrieve wallet and asset data, and monitor activity. Covers event notifications, live data streams, historical backfills, and SQL queries, with guidance for choosing suitable services and access methods.
Organize Nexent test assets into a traceable chain from requirements and bugs to cases, scripts, and results. Review existing coverage, maintain execution settings, and generate a registry and Excel views for formal testing.
Develop and fix Nexent features by connecting written specifications, acceptance criteria, implementation, and verification evidence. Plan unit tests and appropriate staged checks, maintain their links to requirements, and fill confirmed test gaps after development.
Prepare software releases by detecting version files, reviewing changes, and writing changelogs in multiple languages. The workflow updates versions, creates annotated tags with release notes, and can publish GitHub Releases or fill in missing historical releases.
Backfill labels across oh-my-hermes issues and pull requests. Run manually to sweep everything currently unlabeled, or pass a number to triage one item. Use when issues and PRs have accumulated without labels, after adding a new label to .github/labels.yml, or before a release when the backlog needs to be readable by area.
The English summary is being prepared. Showing the original description.
Build and maintain a Stockbee-style daily 20% mover study for US equities by scanning +20%/-20% movers, classifying catalysts and setup context, updating forward outcomes, and summarizing cohort patterns. Use when the user asks to run a daily 20% study, backfill historical 20% movers, find recurring edge patterns, or build a model book of explosive market moves.
The English summary is being prepared. Showing the original description.
Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget. Use this to build a hiring plan, decide which roles to open and in what order, model attrition and backfill, plan for a growth or contraction scenario, or connect headcount plans to the budget.
The English summary is being prepared. Showing the original description.
Map dbt `schema.yml` / `properties.yml` models and sources into ktx semantic-layer overlays and column notes. Covers `sources:` vs `models:`, column `data_tests` (not_null, unique, accepted_values, relationships), and how bundle-time writes complement manifest backfill from git sync. Load when the WorkUnit's `skillNames` includes `dbt_ingest` or when raw files are dbt YAML under `models/` / `sources/`.
The English summary is being prepared. Showing the original description.
Extract facts from meetings and update your knowledge base — person profiles, chronological log, and index. Use when the user asks "ingest my meetings", "update my knowledge base", "extract facts from meetings", "sync meetings to wiki", "backfill knowledge", or wants their PARA/Obsidian/wiki profiles updated from conversation data.
The English summary is being prepared. Showing the original description.
Use when deciding whether an OpenMeld change needs a Changelog entry, writing or publishing an entry, preparing release notes, validating Changelog projections, or historically backfilling missing changes.
The English summary is being prepared. Showing the original description.
Maintain the official OpenMeld Changelog from repository evidence. Use when deciding whether a change needs a Changelog entry, writing or publishing an entry, preparing release notes, validating generated Changelog files, or historically backfilling missing changes.
The English summary is being prepared. Showing the original description.
Create or update a structured change log for a product or platform. Use when someone asks to "create a change log", "log this change", "what changed", "update the change log", "release notes", or "changelog". Reads project memory (CLAUDE.local.md Recent Changes) and meeting notes to build chronological change records. Supports init (backfill from memory), update (append new entries), and release (summarize for a version).
The English summary is being prepared. Showing the original description.
Rules for Operately schema migrations (app/priv/repo/migrations/) and data migrations (app/lib/operately/data/change_*.ex). Use when adding, renaming, reviewing, or generating database migrations, ecto.gen.migration, Operately.Data.Change* modules, backfills, schema_migrations version collisions, mix ecto.migrate, or make gen.migration.
The English summary is being prepared. Showing the original description.
Legacy reference token writer compatibility gate during the DESIGN.md Core v2 catalog cutover.
The English summary is being prepared. Showing the original description.
Use when a database schema or data-meaning change needs Parallel Change, including expand, migrate, and contract sequencing for column renames, type or data reinterpretation, large-table backfills, relationship-table changes, enum/status transitions, timezone/default changes, and index or uniqueness changes. This should trigger before framework-specific Flyway implementation guidance when deciding whether a migration needs a compatibility window or whether a simpler migration is sufficient. Part of Plinth Toolkit
The English summary is being prepared. Showing the original description.
Changes a live Convex schema without downtime: make a field optional, backfill in batches, flip the validator, then clean up. Uses the @convex-dev/migrations component where it fits. Use when renaming or removing a field, changing a type, splitting a table, or when deploy fails with a schema validation error on existing documents.
The English summary is being prepared. Showing the original description.
Design and verify data contracts, schema changes, migrations, rollbacks, backfills, compatibility windows, tenant isolation, and API-to-database field mapping. Use when changing database schema, event payloads, persisted documents, analytics tables, multi-tenant data boundaries, or any user-visible data contract where silent fallback or undeclared fields would be dangerous.
The English summary is being prepared. Showing the original description.
Fix content serving failures caused by metadata (KV store, database) being out of sync with actual storage (GCS, S3, filesystem). Use when: (1) Content exists in storage but API returns "processing" or "not ready", (2) Webhook callbacks that update metadata failed silently, (3) Backfill scripts generated content but didn't update status records, (4) HLS/transcoded content exists but transcode_status is not "Complete", (5) Handler checks metadata status BEFORE checking if content actually exists in storage.
The English summary is being prepared. Showing the original description.
Fix incorrect priority ordering when using denormalized aggregate columns. Use when: (1) Records are processed in wrong order despite ORDER BY on count/sum columns, (2) Top items by some metric aren't being selected first, (3) Aggregate columns show 0 or NULL for records that should have high values, (4) Priority queue processes low-value items before high-value ones. The root cause is often that denormalized columns (vine_count, loop_count, total_orders, etc.) weren't backfilled or maintained properly. Solution: JOIN with source tables to compute actual aggregates at query time.
The English summary is being prepared. Showing the original description.
Think and work like an expert High-Performance Computing Specialist. Use when a task calls for High-Performance Computing Specialist judgment. Reasons from NUMA topology and hybrid MPI+OpenMP+CUDA decomposition through Slurm fairshare/backfill job design, strong/weak scaling (Amdahl/Gustafson), Darshan/mpiP/Nsight profiling, and parallel HDF5/MPI-IO on Lustre while treating I/O storms, collectives bottlenecks, and rank-binding mistakes as first-class failure modes.
The English summary is being prepared. Showing the original description.