Coding standards, frameworks, refactoring, and code review (16.9K skills)
Build Telegram bots, Mini Apps that run inside Telegram, and custom clients using implementation examples. The guide covers message handling, interactive buttons, payments, authentication, storage, and receiving updates through webhooks or long polling.
Develop time-series and event-data solutions with TimescaleDB, an extension for PostgreSQL. The skill provides organized references for installation, time-based tables, ongoing aggregate calculations, compression, and performance troubleshooting.
Use CoinGecko API documentation to build cryptocurrency price trackers and market data integrations. The skill supports implementation and debugging for access to prices, market capitalization, trading volume, and historical data.
Build cryptocurrency exchange integrations with CCXT in JavaScript, Python, or PHP. The skill helps retrieve market data, manage orders, automate trading workflows, check exchange-specific capabilities, and investigate API errors using reproducible examples and logs.
Review NemoClaw issues and pull requests, propose issue types, project priorities, statuses, and labels, then apply only approved changes. Supports individual items and batch triage, with explanations and a report of each update.
Audit and upgrade NemoClaw dependencies, including Hermes and base images. Trace upstream changes to affected code, implement required migrations, and verify tests, distributed artifacts, and the versions actually selected for use.
Compare multiple NemoClaw pull requests addressing the same issue. It checks merge eligibility, correctness, quality, and attribution, then produces an evidence-based recommendation for merging or choosing a candidate for further repair.
Prepare a local NemoClaw development environment, repair setup problems, or check readiness. It also handles explicitly requested command-line access, runtime onboarding, and launching the coding agent pinned by the project.
Find open issues affected by a proposed code change. Identify additional problems it may fix or requested behavior it may conflict with, then report supporting code differences, issue symptoms, and confidence levels.
Publish or update a NemoClaw pull request and track automated checks and reviews through completion. It preserves the requested scope, coordinates repairs for valid findings, and reports the latest commit’s results and remaining blockers.
Turn a named NemoClaw issue into an implementation plan with clear ownership, scope, completion criteria, and validation evidence. For larger changes, define independently useful steps, their dependencies, and delivery order.
Implement or review a managed runtime provider for NemoClaw. Check its required interfaces, activation requirements, saved provider identity, and lifecycle behavior, then report validation evidence and any remaining qualification requirements.
Run one NemoClaw maintainer pass focused on work for a target release. Select a ready pull request, small repair, security concern, or test gap, complete one outcome, and record progress and decisions requiring user input.
Implement an accepted NemoClaw issue or repair a classified pull request finding. Keep changes within the agreed scope, run focused checks for affected behavior, and review the final changes before handing evidence to an authorized publication workflow.
Clean up GitHub issue and pull request titles by removing bracketed NemoClaw tags. It previews proposed changes, applies them after approval, and checks for remaining matches while preserving other tags and plain-text mentions.
Find open NemoClaw security pull requests marked Urgent or High in the project tracker. Connect them to issues, identify competing or superseding proposals, and recommend which request a maintainer should review first.
Answer NemoClaw maintainer questions using policy references covering issue and pull request assessment, labels, project fields, releases, and competing contributions. It explains the relevant rules in plain language through a read-only workflow.
Analyze the full retained history of one NemoClaw pull request to identify contributor, review, and automation delays. Generate a summary and an interactive timeline file, then compare observed timing with a default ten-minute target or a requested alternative.
Develop and test Windows-specific Screenpipe changes on a disposable Azure virtual machine. The workflow verifies native behavior, preserves logs and desktop video, and handles branch and pull request delivery when authorized.
Retrieve and analyze Screenpipe recording engine and desktop app logs to investigate errors or events at a specific time. Get timestamped findings, recurring error patterns, possible causes, suggested fixes, and indications of service status.
Add or modify Tauri commands in the screenpipe desktop app and regenerate TypeScript bindings, the code connecting frontend calls to Rust handlers. Follow the required annotations and checks to keep both sides consistent.
Plan and verify accessibility when changing Handsontable interfaces. Covers keyboard navigation, screen reader messages, focus behavior, and theme contrast, with Playwright tests and axe scans to check changes and resolve reported issues.
Prepare Handsontable changes for review by checking branch names, running required checks, and creating or updating draft pull requests. Fill the project template with test evidence and add changelog entries in the required order.
Add user-facing text to Handsontable through its translation system. The skill covers translation keys, language files, plural forms, right-to-left layouts, preserving Japanese and other East Asian input behavior, and converting text to lowercase according to language rules.