Loading...
Loading...
Found 751 Skills
Use this skill to write, validate, or generate commit messages that follow the Conventional Commits specification.
Implement a project from its documentation and specification. Use when asked to "implement project", "continue implementation", "build from docs", "implement from spec", or when the user wants to progressively implement a documented project following a todo checklist. Reads docs/, creates implementation plans and todo lists, and implements incrementally with tests and commits.
Go Development Guidelines, including naming conventions, error handling, concurrent programming, testing specifications, etc.
OAuth 2.0/2.1 specification expert with deep RFC knowledge and Fastify integration patterns
YQCloud custom Function Calling format specification, designed for ITSM ticket scenarios. It covers the calling specifications and typical processes of four functions: createTicket, getCreateTicketParamJsonSchema, getAllServiceItem, and requestUserSelectServiceItem.
Use when the user wants to validate that implemented code matches its specifications, generate integration tests from feature files, or check if code still satisfies existing scenarios. Trigger after implementation completes a feature. Also use when the user asks "does the code do what we specified?" or "generate tests from the feature files".
Document capabilities and skills comprehensively. Creates skill documentation with examples, specifications, and usage patterns.
Create git commits following the Conventional Commits v1.0.0 specification (conventionalcommits.org). Use when the user asks to commit changes, says "/conventional-commit", or wants a well-structured commit message. Triggers on requests like "commit this", "commit my changes", "create a commit", or any git commit workflow. Analyzes staged/unstaged changes and produces compliant commit messages with proper type, scope, description, body, and footers.
This skill should be used when the user asks to "validate FHIR resources", "check HL7 messages", "validate healthcare data format", "parse FHIR", "HL7 v2 messages", "FHIR R5 validation", "CDA documents", "healthcare data interchange", "FHIR resource schema", "HL7 specifications", or mentions FHIR validation, HL7 message parsing, CDA validation, healthcare data format compliance, or Fast Healthcare Interoperability Resources standards.
OpenHarmony Distributed Soft Bus Code Security Review Expert - Comprehensive inspection of C/C++ code against secure coding standards and logging specifications. Covers over 40 security rules, including key areas such as pointer safety, memory management, lock management, and sensitive information protection. Provides cross-file call analysis and control flow analysis, generating detailed code review reports. Only triggered when user input contains "软总线安全卫士" (Soft Bus Security Guard). ⚠️ Important: This skill is a read-only review tool and does not modify source files.
Chinese functional specification creation tool used to convert natural language feature descriptions into structured functional specification documents. Supports automatic branch name generation, Git branch creation, specification file initialization, and quality verification. Trigger words include: "speckit specification", "functional specification", "create specification", "feature description conversion", "speckit-specify". Use this skill when users need to convert feature ideas into structured specifications.
Validate, audit, and fix agent skills for agentskills.io spec compliance. Use when creating a new skill structure, auditing an existing skill against the specification, fixing common spec deviations, or reviewing frontmatter, directory layout, progressive disclosure, or script interfaces. Triggers on "validate skill", "audit skill", "spec compliance", "fix skill structure", "skill frontmatter", "SKILL.md format", or "agent skills spec".