Loading...
Loading...
Found 174 Skills
Unified management of SVG icons in React TypeScript projects; supports icon component encapsulation, naming conventions, and migration guidance; applicable to scenarios such as project icon refactoring, new project icon specification formulation, and icon maintenance optimization
Pipeline state management for Goldsky Turbo — pause, resume, restart, and delete commands with their rules and safety behavior. Use this skill when the user asks: will deleting my pipeline lose the data already in my postgres/clickhouse table, how do I pause a pipeline while doing database maintenance, how do I restart from block zero to reprocess all historical data, can I update a running streaming pipeline in place or do I have to delete and redeploy, will resuming a paused pipeline pick up from where it left off (checkpoint), how do I re-run a completed job pipeline from the beginning, can I pause or restart a job-mode pipeline. Also covers what happens to checkpoint state on delete, and job auto-deletion 1 hour after termination. For actively diagnosing why a pipeline is broken or erroring, use /turbo-doctor instead.
Review code after implementation work to identify design flaws, abstraction issues, or maintenance risks that only became clear once real code was written. Use whenever the user asks whether a recent change exposed architectural problems, whether an abstraction is fighting the implementation, or whether a refactor is justified. Be conservative and avoid suggesting refactors without concrete evidence of recurring cost or complexity.
Audit and maintain the health of the Obsidian wiki. Use this skill when the user wants to check their wiki for issues, find orphaned pages, detect contradictions, identify stale content, fix broken wikilinks, or perform general maintenance on their knowledge base. Also triggers on "clean up the wiki", "what needs fixing", "audit my notes", or "wiki health check".
When the user says phrases like "update the index", "add this to the index", "added a new file", "added a new book/note/document", "need to update the material library index", the **Incremental Maintenance Mode** of this skill should be used. When the user says phrases like "index health check", "index体检", "check the index", "sync the index", "fill in missing index entries", the **Health Check Mode** of this skill should be used to scan all libraries ↔ INDEX to find missing/invalid entries and batch fill them in. Applicable to all libraries with INDEX.md: Reading Notes Library, Core Concepts Library, Viral Script Library, 04-Methodology Precipitation, and any newly created libraries in the future. The value of an index depends on content accuracy—you must fully read the original text before writing; inferring based on file names or impressions will render the index useless for reference. Even if the user only says "I added a file" or "put this in", as long as it involves the index, this skill should be triggered. Do NOT trigger for: Only viewing the index (directly Read), deepening topics (use li-topic), generating scripts (use li-writer). Use when the user adds new content to any indexed library, OR runs a global index health-check to find missing/stale entries.
This skill should be used when the user asks to 'set up memory', 'create memory files', 'create MEMORY.md', 'set up topic files', 'improve memory organization', 'what should I remember', 'how to structure memory files', 'MEMORY.md is too long', 'what goes in memory vs topic files', 'memory best practices', or wants to establish a persistent knowledge base across Claude Code sessions. Triggers on: memory setup, MEMORY.md, topic files, cross-session knowledge, persistent notes, memory maintenance, memory pruning.
Help users manage technical debt strategically. Use when someone is dealing with legacy code, planning refactoring work, deciding between rewrites vs. incremental fixes, trying to get buy-in for tech debt reduction, or balancing new features with maintenance.
Umbrella skill for agent work discipline across development, analysis, and documentation: inspect the repo before restructuring, keep durable truth in repo artifacts instead of chat memory, co-evolve specs/design/steering/user docs with code, apply sound coding patterns, verify work honestly, avoid shortcuts, work efficiently with subagents without hallucinating, and keep moving through the next concrete work item when the human is away. References cover coding patterns, AI-authored code review, and artifact co-evolution. Trigger when the user asks for workflow discipline, coding patterns, doc/artifact maintenance, code review of AI-authored code, project hygiene, execution guardrails, repo normalization, or when a task risks drifting across architecture, storage, specs, continuity, or tooling boundaries.
Analyze A-share stocks using fixed scripts, supporting the maintenance of local watchlists and position pools, fetching individual stock and concept sector data, querying risks such as financial report disclosures and share reduction announcements, and outputting structured recommendations including Buy, Watch, Hold, Reduce Position, and Sell. Suitable for scenarios where you need to update local stock pools, fetch real-time data, compare the top three strongest stocks in a concept sector, or generate transaction analysis with risk prompts.
Interactive macOS system cleanup for any dev machine. Frees disk space by pruning caches, package managers, unused apps, stale dev artifacts, and more. Discovers what's installed rather than assuming a specific setup. Always consults the user before deleting anything. Use when the user asks to: clean up their Mac, free disk space, remove unused apps, prune caches, clean developer artifacts, or any disk space maintenance task.
Extract a validated learning from the current session, store it in the central agent learnings file, and sync the resulting Learnings section into the agent definitions used by the supported CLIs. User-only maintenance workflow for durable agent guidance.
Use this skill for Sealtun-specific local-to-public tunnel work or Sealtun repo maintenance/release. Trigger for sealtun, sealtun.yaml, Sealos tunnel, ngrok/cloudflared-style tunnel, expose localhost/local port/local dev server, public HTTPS URL/domain for local app, public SSH/TCP tunnel, NodePort SSH, ProxyCommand fallback, webhook/payment/OAuth/bot callback to local service, preview/demo link, custom domain/CNAME, Basic Auth, Bearer token, IP allowlist/denylist, temporary access links, ttl auto-expire, apply/diff multi-tunnel config, stop/start/resume, cleanup, daemon/session/logs/metrics/dashboard/doctor, npm binary packages, GitHub Release, GoReleaser, GHCR. Chinese triggers: 内网穿透, 本地服务公网访问, 本地端口暴露, localhost 暴露到公网, 公网预览链接, 公网域名, 公网 SSH, SSH 隧道, TCP 隧道, 第三方回调到本地, 隧道认证, 访问控制, 声明式配置, 发版. Do not use for generic Kubernetes/Ingress/DNS/SSH unless Sealtun is involved.