Loading...
Loading...
Found 6,725 Skills
Use the codeintel command-line tool: intelligent indexing and field trace query for Go codebases. Features include building indexes (init), querying symbol/field read-write summaries (query fields), field tracing (trace-backward/forward), full-chain data value tracing (value-trace), call relationship analysis (callers/callees/impact), export (export), and Web service (serve). This skill is used when users request to analyze field data flows in Go codebases, trace field users/producers, check function field read-write operations, or query call relationships.
Use ae-cli for AE/TE analysis-side data questions, asset operations, and asset governance: reports, analysis boards, BI dashboards, ad-hoc models, drilldown, detail data, alerts, clusters, tags, metrics, metadata, project configuration, tracking plans, governance asset lists/rules/lineage/impact/dependency, batch asset operations, projects, and resource links. Use when the user asks to query data, explain a change, export evidence, or inspect/create/update/govern analysis assets.
Use hexagonal architecture for external systems; define ports (interfaces) and per-provider adapters; select adapter at composition edge
SAP-RPT-1-OSS local tabular prediction workflows for FI/CO prototype datasets. Use when preparing SAP finance CSV exports for classification or regression experiments with source-verified setup, leakage checks, and governance review.
Planning a whole-codebase simplification: audits a Go/TS codebase for needless abstraction and emits a KILL/REVIEW/KEEP plan plus a ring:running-dev-cycle task array. Plans only — no edits. Detects single-impl interfaces, pass-through shims, translation-free adapters, and dead-code cascade chains under an inverted burden of proof. Use for pre-public or post-pivot cleanup. Skip for current diff review (use ring:reviewing-code).
Running the backend dev cycle: implements every task in a rolling-wave plan.md (ring:writing-plans format) for a Go/TS service, driving specialist agents through Gate 0 implementation/TDD, Gate 8 parallel review, and Gate 9 validation per epic, elaborating later phases at each phase boundary. Use when starting or resuming a gated backend dev cycle with a plan.md (legacy tasks.md only for cycles already in flight; new cycles need the canonical plan format). Skip for frontend (use ring:running-dev-cycle-frontend) or docs-only work.
Review Go and TypeScript code for performance problems — allocations, GC pressure, O(n²) algorithms, N+1 queries, unbounded concurrency, blocked event loops, re-render storms. Works on uncommitted changes, a commit range, a branch, or a full PR. Use when the user says "perf review", "check performance", "find bad allocs", "is this slow", "review allocations", "will this scale", or asks for a performance pass on a diff, branch, or PR. Do not use for general correctness review or style review — this skill only hunts performance.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Edit images with Google Nano Banana 2 (image-to-image edit endpoint) on RunComfy. Documents Nano Banana Edit's strengths (preserve subject identity, swap background, localize edits with spatial language, multi-image batch edits up to 20 inputs), the schema, and when to route to GPT Image 2 edit / Flux Kontext / Nano Banana 2 t2i instead. Calls `runcomfy run google/nano-banana-2/edit` through the local RunComfy CLI. Triggers on "nano banana edit", "edit with nano banana", "image edit nano banana", or any explicit ask to edit with this model.
Chart a route through a foggy problem — turn a loose idea into a map of investigation tickets and resolve them one at a time until the way to the goal is clear.
Relight a still image — change the lighting setup, color temperature, direction, or mood — on RunComfy via the `runcomfy` CLI. Routes to Qwen Edit 2509's dedicated `relight` LoRA endpoint for purpose-built relighting, with fallback to identity-preserving edit endpoints (Nano Banana 2 Edit, GPT Image 2 Edit, FLUX Kontext Pro) when prose lighting language is enough. Use for product relighting (studio softbox → window light), portrait mood shift (overcast → golden hour), or color-grade change. Triggers on "relight", "relighting", "change the lighting", "make it golden hour", "studio lighting", "rim light", "blue hour", "soft window light", "change light direction", "color temperature", or any explicit ask to alter how a still is lit.
Feishu Video Conference: Allow bots to join/leave ongoing meetings on behalf of the current user, and read real-time events during the meeting (participant join/leave, speaking, chatting, screen sharing, etc.). 1. When users provide a 9-digit meeting number and request to join or leave on their behalf, use +meeting-join / +meeting-leave — this will generate actual join/leave records. 2. During a meeting, when users want to know in-meeting dynamics such as "who joined", "who left", "who is speaking", "is someone sharing their screen", the bot can use +meeting-events to read the event timeline after joining the meeting. 3. Typical scenarios: Meeting participant bot, in-meeting assistant, proxy attendance, proxy participation. Prerequisite: The bot can only read events of meetings that it has joined and are still ongoing; to query the participant list, minutes, or transcript of an ended meeting, please use the lark-vc skill.