Loading...
Loading...
Found 1,645 Skills
Bootstraps a new AI-assisted project through a structured 4-phase conversation, then generates PROJECT.md, JOURNAL.md, .gitignore, and tmp/README.md. Also searches skills.sh and installs relevant skills for the approved tech stack. Use when starting a new project from scratch or when no PROJECT.md exists in the current directory. Do NOT trigger if PROJECT.md already exists — redirect to /project-sync instead. Invoke with /project-init — never auto-trigger.
Implements Syncfusion WinUI RangeSlider (SfRangeSlider) control for range selection in desktop applications. Use this when working with range selectors, dual-thumb sliders, or numeric range selection interfaces. This skill covers configuration, labels, ticks, dividers, track customization, thumb styling, tooltips, and value handling for interactive range selection in WinUI applications.
OpenTelemetry with Grafana stack. Covers OTel SDK instrumentation for Go/Java/Python/Node.js/.NET, OTLP protocol and endpoint configuration, sending telemetry to Grafana Cloud via OTLP endpoint, Grafana Alloy as OTel collector, sampling strategies, Kubernetes OTel Operator, and migration from other observability tools. Use when instrumenting apps with OTel, configuring OTLP endpoints, setting up collectors, or migrating to OpenTelemetry.
Grafana Tempo distributed tracing backend. Covers TraceQL query language (span selectors, attribute scopes, pipeline operators, structural operators, metrics functions), trace ingestion via OTLP/Jaeger/Zipkin, Tempo architecture (distributor/ingester/compactor/querier/metrics-generator), full configuration reference with YAML, metrics-from-traces (span metrics, service graphs, TraceQL metrics), deployment modes (monolithic/microservices/Helm/Kubernetes), multi-tenancy, performance tuning, caching, and HTTP API. Use when working with distributed traces, writing TraceQL queries, deploying Tempo, configuring trace pipelines, or setting up Grafana-Tempo integrations (traces-to-logs, traces-to-metrics, traces-to-profiles).
Two-way sync between a local paper directory and an Overleaf project via the Overleaf Git bridge (Premium feature). Lets you keep ARIS audit/edit workflows on the local copy while collaborators edit in the Overleaf web UI. Token never touches the agent — user does the one-time auth via macOS Keychain. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to bridge their ARIS paper directory with an Overleaf project.
Break down a requirement that is "too large to be implemented as a single feature" into a list of sub-features with dependencies and statuses, and place it in the independent `codestable/roadmap/{slug}/` directory — serving as the seed and scheduling basis for subsequent multiple feature processes. Two modes: new (draft a new roadmap from a large requirement), update (refresh an existing roadmap: add items, modify dependencies, reorder, mark as drop). Division of labor with requirements / architecture — those two record "what the system is now", while the roadmap records "what we plan to do next". Trigger scenarios: Users say "I want an X system", "Help me break down this requirement", "Schedule this large requirement", "Create a roadmap", or it is found during the feature-design phase that the requirement is too large to fit into a single feature.
BetaList platform help — pre-launch startup discovery directory where early adopters find startups before they make it big (15,000+ featured startups, 100K+ early adopters, DR67 dofollow backlink). Covers submission optimization, acceptance criteria (21% acceptance rate), free queue vs $129 Priority listing, newsletter inclusion (30K+ subscribers), listing best practices, and API access. Use when your startup needs early adopter signups, BetaList submission got rejected, not sure if Priority listing is worth $129, or listing isn't attracting enough interest. Do NOT use for multi-directory launch strategy (use /sales-launch-directory). Do NOT use for Product Hunt (use /sales-producthunt).
Use Neo4j GenAI Plugin ai.text.* functions and procedures for in-Cypher embedding generation, text completion, structured output, chat, tokenization, and batch ingestion. Covers ai.text.embed(), ai.text.embedBatch(), ai.text.completion(), ai.text.structuredCompletion(), ai.text.aggregateCompletion(), ai.text.chat(), ai.text.tokenCount(), ai.text.chunkByTokenLimit(), and provider configuration for OpenAI, Azure OpenAI, VertexAI, and Amazon Bedrock. Requires CYPHER 25. Replaces deprecated genai.vector.encode(). Use when writing pure-Cypher GraphRAG, embedding nodes in-graph, generating structured maps from prompts, or calling LLMs inside Cypher queries. Does NOT handle neo4j-graphrag Python library pipelines — use neo4j-graphrag-skill. Does NOT handle vector index creation/search — use neo4j-vector-index-skill.
End-to-end testing patterns with Playwright for full-stack Python/React applications. Use when writing E2E tests for complete user workflows (login, CRUD, navigation), critical path regression tests, or cross-browser validation. Covers test structure, page object model, selector strategy (data-testid > role > label), wait strategies, auth state reuse, test data management, and CI integration. Does NOT cover unit tests or component tests (use pytest-patterns or react-testing-patterns).
Compile-time dependency injection in Golang using google/wire — wire.NewSet, wire.Build, wire.Bind (interface→concrete), wire.Struct, wire.Value, wire.InterfaceValue, wire.FieldsOf, cleanup functions, //go:build wireinject injector files, and generated wire_gen.go. Apply when using or adopting google/wire, when the codebase imports `github.com/google/wire`, or when wiring an application graph at compile time via `wire.Build`. For runtime DI with reflection, see `samber/cc-skills-golang@golang-uber-dig` skill.
Novel content polishing and optimization, suitable for user requests such as "Help me polish this novel", "Improve the writing style", "Optimize chapter rhythm", "Enhance this highlight", "Make dialogues more natural", "Make this passage more engaging", "Optimize novel writing style", "Adjust chapter rhythm", "Make dialogues more realistic", "Help me revise this content", "Polish novel", "Optimize highlights", "Improve writing style", "Make this passage more immersive", etc. It provides 3 levels of polishing, focusing on optimization of writing style and content, supporting special optimizations such as style adaptation, rhythm tightening, highlight enhancement, dialogue optimization, etc. **Polished results directly modify the chapters/ directory, and automatic backups are made to .sumeru/write/original/ before modification**. **Sub-Agents are used for parallel processing during batch polishing, with each Agent responsible for a maximum of 3 chapters**
Open Orbit briefing skill — selected by the Orbit pipeline when Gmail is the user's only connected connector, or when the user explicitly scopes their daily digest to Gmail. Pulls the past 24 hours of inbox activity (replies awaited, mentions, cc, auto- categorized bulk) from the user's authenticated Gmail connection and renders the digest as the Orbit Daily Digest email opened inside Gmail's reading view. This skill should not be triggered manually — it is invoked by Orbit's daily-digest scheduler against live Gmail data.