534 skills · sorted by relevance
Organize research knowledge by project in Obsidian, from creating folder structures and routing notes to maintaining daily logs, plans, and indexes. It also manages note changes and coordinates checks for broken links and registry consistency.
Record completed steps, decisions, issues, and next actions in dated progress logs. Maintain recent task history and sync updates to shared storage so an agent can recover context and resume work after a session reset.
Switch Codex from Weave Router back to its normal provider for future sessions. Keep the existing login and router configuration, receive the command result, and retain the option to turn routing on again later.
Switch Codex from Weave Router back to its default provider without logging out or deleting the router configuration. The change applies the next time Codex starts and can be reversed with `$router-on`.
Launch Remotion Studio to preview a video in a browser while it is being created or edited. Keep the preview open to review changes, and choose browser behavior, server ports, or logging options.
Write JavaScript for actions/github-script@v8 in GitHub Actions. Apply consistent logging, pass outputs and environment variables to later steps, publish readable summaries, and handle errors with the action's provided utilities.
Build CI workflows that use mirrord to test applications against services in a real Kubernetes cluster. Configure runner access, start and stop application sessions, validate configuration files, and troubleshoot connection, permission, and logging problems.
Save decisions, research findings, and work updates to Obsidian, then update related notes, daily entries, and task boards. Maintain existing pages, preserve changing facts with their history, and check for duplicates and broken links.
Organize a knowledge base into preserved sources, draft research, and stable articles. Follow rules for document status, cross-links, replacement history, and change logs so established knowledge remains traceable to its original evidence.
Guide Python module additions and refactoring in APM CLI. Uses existing architecture patterns to organize shared logic and decision ownership, with regression tests and static checks to protect changes that centralize behavior.
Improve APM CLI commands, help text, setup flows, and error messages. The skill checks consistency with familiar developer tools and guides wording so users understand failures and know what action to take next.
Automatically send Claude Code conversations and tool calls to Braintrust. View nested activity records that connect each session, conversation exchange, and operation, including file reads, edits, and terminal commands, to inspect how coding work unfolded.
Find and replace code using syntax patterns with ast-grep. Search for function calls, imports, and definitions while excluding matches inside strings or comments, then preview proposed replacements before applying changes across selected files or directories.
Build Python agents with Agentica SDK using function decorators or agent instances. Examples cover conversation memory, external tools, MCP connections for tool access, multi-agent coordination, typed results, and logging to help implement and debug agent behavior.
Publish videos or image posts to 抖音 through its creator dashboard using Playwright browser automation. The workflow covers login, prepublication checks, user confirmation, optional SMS verification, and checking the published item against the creator’s content list.
Publish image posts or videos to 小红书 (XHS), with QR code login and saved login sessions. Check titles and media files before posting, review the final content, and verify whether publication succeeded through browser automation.
Domain routing and boundary guidance for authorized defense evasion and bypass testing, including WAF bypass, AV/EDR evasion, logging considerations, and traffic obfuscation. Use when a task belongs to the evasion domain and needs scope, evidence, pivot, or exit criteria.
The English summary is being prepared. Showing the original description.
Track ML experiments with automatic logging, visualize training in real-time, optimize hyperparameters with sweeps, and manage model registry with W&B - collaborative MLOps platform
The English summary is being prepared. Showing the original description.
Deep learning framework (PyTorch Lightning). Organize PyTorch code into LightningModules, configure Trainers for multi-GPU/TPU, implement data pipelines, callbacks, logging (W&B, TensorBoard), distributed training (DDP, FSDP, DeepSpeed), for scalable neural network training.
The English summary is being prepared. Showing the original description.
Use this skill when the user is doing hands-on DOCA Telemetry Exporter programming on a host where DOCA is installed — defining a doca_telemetry_exporter_schema and event types, creating sources, picking a publish surface (typed events / opaque events / the metrics counter-gauge-histogram API / OTLP logs / NetFlow), walking the schema-then-source lifecycle, or debugging DOCA_ERROR_* failures from the exporter API. Trigger even when the user does not explicitly mention "DOCA Telemetry Exporter" or "doca_telemetry_exporter_*" — typical implicit phrasings include "publishing counters from my DOCA app", "BAD_STATE when I report an event", "consumer/DTS sees nothing but my report succeeded", "how do I export NetFlow/IPFIX records", or "should I link the exporter or the telemetry service". Refuse and route elsewhere for the receiving DOCA Telemetry Service (DTS), plain stdout logging via doca_log, or real-time event subscription back into the app via doca-comch — those belong to other skills.
The English summary is being prepared. Showing the original description.
Use this skill to read DOCA hardware-counter events from a `doca_dev` through the per-domain Telemetry reader libraries: `doca_telemetry_pcc`, `_dpa`, `_diag`, `_adp_retx`, `_phy`, and `_pci`. It covers capability checks, context creation, startup, and per-domain reads or samples. Trigger for implicit requests such as "read PCC counters from my BlueField app", "sample DPA counter exports", or "expose PHY, PCI, or DIAG counters from this doca_dev". This is the counter-reader surface, not a NetFlow, IPFIX, or local-socket collector. Route publishing and export to `doca-telemetry-exporter`; route the deployed DOCA Telemetry Service to `doca-dts`, and collectors and plain stdout logging elsewhere.
The English summary is being prepared. Showing the original description.
Structured logging extensions for Golang using samber/slog-**** packages — multi-handler pipelines (slog-multi), log sampling (slog-sampling), attribute formatting (slog-formatter), HTTP middleware (slog-fiber, slog-gin, slog-chi, slog-echo), and backend routing (slog-datadog, slog-sentry, slog-loki, slog-syslog, slog-logstash, slog-graylog...). Apply when using or adopting slog, or when the codebase already imports any github.com/samber/slog-* package.
The English summary is being prepared. Showing the original description.
Golang library and framework selection — vetted production-ready options by category (web, database, testing, logging, messaging), new and experimental stdlib packages, standard-library-first tradeoffs, and maturity signals (maintenance, license, importer counts). Apply when the user asks for library suggestions, wants to compare alternatives, needs to choose a library for a specific task, or when a new dependency is being added to the project. Not for a specific library's API once chosen (→ See that library's dedicated skill, e.g. `samber/cc-skills-golang@golang-samber-lo`), nor for go.mod mechanics, upgrades, or vulnerability audits (→ See `samber/cc-skills-golang@golang-dependency-management` skill).
The English summary is being prepared. Showing the original description.
Reactive streams and event-driven programming in Golang using samber/ro — ReactiveX implementation with 150+ type-safe operators, cold/hot observables, 5 subject types (Publish, Behavior, Replay, Async, Unicast), declarative pipelines via Pipe, 40+ plugins (HTTP, cron, fsnotify, JSON, logging), automatic backpressure, error propagation, and Go context integration. Apply when using or adopting samber/ro, when the codebase imports github.com/samber/ro, or when building asynchronous event-driven pipelines, real-time data processing, streams, or reactive architectures in Go. Not for finite slice transforms (→ See `samber/cc-skills-golang@golang-samber-lo` skill).
The English summary is being prepared. Showing the original description.