Discover DevOps skills, compare source repositories and read the instructions for each workflow.
Phase 1 of Ontology Builder Pipeline. Ingests and catalogs all input materials from _input/ folder. Use when starting ontology building process or when processing new input documents for domain analysis.
Phase 4 of Ontology Builder Pipeline. Generates final Ontology artifacts (entity definitions, workflow catalog, concept guides) from DRD. Use after Phase 3 DRD is complete.
Phase 2 of Ontology Builder Pipeline. AI acts as domain SME to analyze raw inputs, extract entities/workflows/rules, fill knowledge gaps using market expertise. Use after Phase 1 ingestion is complete.
Phase 3 of Ontology Builder Pipeline. Synthesizes analysis results into complete Domain Requirement Document (DRD). Use after Phase 2 analysis is complete to generate structured DRD.
Independent verification agent for Ontology Builder Pipeline. Cross-validates outputs against inputs, checks traceability, validates constraints, and identifies issues. Use as a separate agent to verify pipelin...
Knowledge about the Charm ecosystem (Bubbletea, Lipgloss, Bubbles) used for the Drime Shell UI. Use when creating or modifying UI components, styling output, or handling user interaction.
Knowledge about Drime Cloud API endpoints, authentication, file operations, workspaces, vault encryption, and S3 upload flow. Use when working with API integration, adding new endpoints, or debugging API issues...
Knowledge about the project's CI/CD pipeline, Semantic Versioning with Conventional Commits, release-please automation, and GoReleaser. Use when working with releases, commits, or CI workflows.
Use this skill when monitoring OUC system state for anomalies or changes. Detects upgrade events, auditor pool changes, proposal status, and triggers appropriate actions. Part of the Self-Amending Protocol AI A...
Use this skill when you need to query on-chain data from EVM or ICP. This includes: ERC-7546 Dictionary state, OUC canister state, auditor pools, proposals, and upgrade status. Provides helper functions for cas...
Best practices for writing Claude Code skills and agents. Use when creating, improving, or troubleshooting SKILL.md or agent files.
Generate bulletproof HTML email code that renders correctly across Gmail, Outlook, Apple Mail, Yahoo, and mobile clients. Use when creating HTML emails, email templates, or any HTML content for email delivery....
Prevent generic AI-generated email aesthetics and enforce distinctive, handcrafted design quality. Use when generating HTML emails, email templates, newsletters, marketing emails, or any email content. Ensures...
Apply sophisticated design system principles to HTML emails including typography hierarchy, color palettes, spacing systems, and layout patterns. Use when creating email templates that need cohesive, intentiona...
Use when upgrading .c3/ documentation to current skill version - reads VERSION, applies transforms from migrations/ directory in batches
Use when changes affect component organization, technology stack, or cross-container communication - triggered by new components, pattern changes, or needing to map external interfaces to internal components
Use when exploring Context level impact during scoping - system boundaries, actors, cross-container interactions, and high-level concerns
Use when bootstrapping C3 documentation for any project - guides through Socratic discovery and delegates to layer skills for document creation
Use when documenting component implementation patterns, internal structure, or hand-off points - enforces NO CODE rule and diagram-first approach for leaf-level C3 documentation
Use when verifying C3 documentation quality - checks methodology compliance (layer rules, structure, diagrams) and implementation conformance (docs vs code drift)
Use when making changes to diashort - new features, bug fixes, refactoring, or modifications. Guides through brainstorming, planning, and subagent-driven implementation with reviews.
Use when configuring project preferences in .c3/settings.yaml - diagram tools, layer guidance, guardrails, and handoff steps
Use when designing, updating, or exploring system architecture with C3 methodology - iterative scoping through hypothesis, exploration, and discovery across Context/Container/Component layers
功能开发完成后的验证流程 - 构建 WASM 并启动开发服务器进行预览测试
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.