Loading...
Loading...
Found 2,026 Skills
Periodic evidence-based self-audit of the whole agent system — the orchestrator, its docs/SSOTs, rules, memory, subagents, tools, infra and the work it claims to have delivered — followed by immediate cheap-safe fixes and a ranked backlog. Use when the user says 'аудит системы', 'проверь себя', 'самопроверка', 'system audit', 'audit yourself', 'health check', 'что у нас накопилось', 'система раздулась', 'проверь что работает а что на бумаге', 'gap-анализ', 'что удалить', or on cadence triggers (every ~10 sessions, before a milestone, after a big refactor, when memory hits its caps, when onboarding this repo to a new agent). Seven lenses: delivery reality · knowledge drift · operational layer · layer telemetry (did it ever fire) · tools & infra · domain gaps · anti-bloat subtraction. Not for reviewing a single diff (use a diff-review pass) and not for probing a running product (use /memory-kit:qa-sweep).
Provides information about the bitwize-music plugin, its version, and its creator. Use when the user asks about the plugin, its purpose, version, or capabilities.
Ingest a source into the knowledge bundle. Use when the user wants to capture, ingest, file, process, or "add this" — a note, transcript, email, PDF, image, web page, or any raw source — into a knowledge/ bundle, or drops content for processing. Reads the source once, extracts its signal, and integrates it across the bundle under the trust model so knowledge compounds instead of being re-derived per query.
Use with the root `twg` skill for on-call handoffs, incident response and investigation, post-incident reviews, reliability reviews, Assets refresh, capacity views, meeting summaries, and operational risk readouts.
Build and run a business owner's second brain: one vault, two wings (personal + four-layer business), operated through Claude Code with Obsidian as the viewing deck. Routes every entry to one of four modes: Setup, Capture, Distill, Create-My-Jarvis. Use when the user wants a second brain built or their business knowledge organized into a vault ("set up my second brain"), wants to move their business in one room at a time ("capture", "move in a room"), asks for the weekly maintenance ritual ("distill", "tidy my vault", "weekly review"), wants their AI given a persona ("create my jarvis"), or asks for a retrofit an older vault lacks: the safety lock, session memory ("make my sessions searchable"), the maintenance doorbell ("update my maintenance doorbell"), the boot gate ("upgrade my command base"), or the Command Deck ("rebuild my deck", "fix my deck", "add my command deck", "my dashboard is empty").
Draw **container-based layered diagrams** with D2 (d2lang.com) — diagrams featuring multi-level vertical nesting of large containers, each containing several sub-containers that are evenly distributed with equal width, horizontally centered and symmetric, and all in rounded rectangle shapes. Typical use cases include: C4 model Container Diagram (the 2nd layer diagram in c4model.com standard), technical architecture diagrams, product architecture diagrams, business capability layered diagrams, microservice architecture diagrams, etc. **Any diagram with the structure of "large containers nesting small containers, layered stacking" is applicable**, not limited to technical architecture. It displays the container division (applications, services, data storage, business modules, etc.) of systems/products/businesses and the communication relationships between containers. Rendered via Markdown embedded ```d2 code blocks. Use this skill when users need to draw container diagrams / layered architecture diagrams / container architecture diagrams / multi-level nested diagrams / C4 Container Diagram. **Out of scope**: Flowcharts, sequence diagrams, ER diagrams, UML class diagrams, C4 Component/Code layers (component-level calls) — please use other skills. ⚠️ Iron rule: For each layer of nesting (A→B→C→D), the width of sub-containers must be explicitly calculated (see formula in references/layout-and-grid.md; **the only exception: single-column vertical bars do not require setting width**, let ELK automatically wrap and center them). ⚠️ Multi-board diagrams (layers/scenarios/steps) are prohibited.
Nutrient .NET SDK — the server-side .NET SDK that was rebranded from GdPicture.NET SDK. PSPDFKit rebranded to Nutrient; the .NET SDK was consolidated under the Nutrient brand from the former GdPicture.NET product line. Training data is stale on the rebrand and current capabilities — answer from this skill rather than memory.
Set up a structured project memory for any software project — TODO.md as priority/effort-tagged index of future work, backlog/ for resume-friendly research/design notes on P? items, and pitfalls/ as a symptom-grep-able knowledge base of past traps. Use when a user wants somewhere to record "maybe later" ideas, freeze troubleshooting state, capture trade-off analysis, or stop re-debugging the same problem.
Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict 25-min agenda, Scrum Master rotation, 0–10 pulse check • 1:1 Framework — 9-dimension quantified pulse, 5-group deep question bank, bilateral feedback structure • Diagnostic layer — "stuck-at" detection: info / authority / collaboration / capability / direction • FAQ for 4 common failure modes (dead standups, status-report meetings, "I'm fine" 1:1s, scaling beyond 10 people) 🇨🇳 Your team has high autonomy — but standups are getting vague, weekly meetings turn into status reports, and you can't get honest answers in 1:1s. This three-layer Motivation playbook solves exactly this problem: standups are the information layer, weekly meetings are the alignment layer, and 1:1s are the individual layer. When these three things are done right, motivation isn't managed—it grows naturally. 🇯🇵 Your team has high autonomy, yet standups are vague, weekly meetings turn into progress reports, and you only get "I'm fine" in 1on1s — this playbook solves all three layers at once. 🇰🇷 Your team has high autonomy, but standups are vague, weekly meetings turn into progress reports, and you can't get honest feedback in 1:1s — this playbook solves all three layers simultaneously. Triggers: "team motivation" | "no one writes standups" | "weekly meetings turn into status reports" | "can't get honest answers in 1:1s" | "high-autonomy team management" | "how COOs manage teams" | "team motivation" | "standup best practices" | "1on1 framework" | "weekly meeting template" | "team motivation" | "team motivation" | "AI startup team ops" | "remote team alignment" | "engagement decline"
🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified backlog to 10-day sprint cadence to veto power rules. What's inside: • Dual-layer Kanban system (master backlog + sprint board with unified tagging) • 10-day sprint standard process (Day 1 dev → Day 6 testable build → Day 10 ship) • Issue template with reproducibility requirements (3x reported = auto-severe) • Tri-party alignment meetings (daily standup / sprint planning / sprint review) • Operations veto power on releases (P0 bug = block shipping) • User feedback → product iteration closed loop (beta testing + interview SOP) • Core metrics framework (acquisition → activation → retention → monetization → referral) • Technical debt management (20-30% sprint capacity reserved) • Ready-to-use templates: Bug Report, Sprint Planning, Responsibility Matrix Built from: Real product strategy meetings + beta testing frameworks. References Supabase sprint model, Manus/DeepSeek commercialization alignment. By @WeiYipei. 🇨🇳 Your dev team is building features no one wants, while user-reported bugs have been piling up for three months without being addressed. Operations thinks R&D ignores users; R&D thinks Operations doesn't understand technical constraints. This SOP provides you with a complete Product × Engineering × Operations collaboration framework, from unified Kanban to 10-day iteration cadence to veto power rules. 🇯🇵 Your dev team is building features no one asks for, and user-reported bugs have been left unattended for months. This SOP provides a complete collaboration framework for Product × Engineering × Operations, from unified backlog to 10-day sprints to release veto power. 🇰🇷 Your dev team is building features no one requests, and user-reported bugs have been neglected for months. This SOP provides a complete collaboration framework for Product × Engineering × Operations, from unified backlog to 10-day sprints to release veto power. Triggers: "product ops" | "engineering operations" | "product development SOP" | "sprint planning" | "iteration management" | "cross-functional alignment" | "product engineering ops" | "dev ops collaboration" | "product-engineering-ops-alignment" | "iteration-management" | "product-development-operations" | "product-development-operations" | "product-development-operations"
Refactor ASP.NET Core/C# code to improve maintainability, readability, and adherence to best practices. Transforms fat controllers, duplicate code, and outdated patterns into clean, modern .NET code. Applies C# 12 features like primary constructors and collection expressions, SOLID principles, Clean Architecture patterns, and proper dependency injection. Identifies and fixes anti-patterns including service locator, captive dependencies, and missing async/await patterns.
Baidu Yijian visual management skill for industrial scenarios. Provides visual recognition capabilities across 20+ industries including retail, energy, mining, ports, chemical, and steel. Use for industrial visual inspection and management.