Loading...
Loading...
Found 7,638 Skills
Updown.io integration. Manage data, records, and automate workflows. Use when the user wants to interact with Updown.io data.
Stability AI integration. Manage data, records, and automate workflows. Use when the user wants to interact with Stability AI data.
Awesome Support integration. Manage data, records, and automate workflows. Use when the user wants to interact with Awesome Support data.
Fidel integration. Manage data, records, and automate workflows. Use when the user wants to interact with Fidel data.
SAP Ariba integration. Manage data, records, and automate workflows. Use when the user wants to interact with SAP Ariba data.
Zoho Expense integration. Manage data, records, and automate workflows. Use when the user wants to interact with Zoho Expense data.
Browse AI integration. Manage data, records, and automate workflows. Use when the user wants to interact with Browse AI data.
Worldline integration. Manage data, records, and automate workflows. Use when the user wants to interact with Worldline data.
Issue Workflow Stage 3——Fix code precisely based on confirmed root cause and solution, verify the effect, and document it in {slug}-fix-note.md. This is the final stage of the issue workflow—no verification loop means the workflow is incomplete. Two entry points: the standard path is triggered from easysdd-issue-analyze (with existing {slug}-analysis.md), and the quick path is triggered directly from easysdd-issue-report (without {slug}-analysis.md, as the root cause was determined by AI reading code during the report stage). Trigger scenarios: user says 'Start fixing the bug', 'Fix according to analysis', 'Start modifying code'. During repair, only modify the files stated in the solution; do not optimize casually or introduce new abstractions—these actions will make the scope spread to untraceable levels.
Phase 1 of the feature workflow — Draft a design document for the new feature, which serves as the sole input for subsequent implementation and acceptance. First gather evidence (read architecture docs, review relevant code, grep to prevent term conflicts, check archives), then write a complete first draft in one go (including YAML frontmatter + three-layer structure + test design), submit it to the user for overall review, and iterate until approval. After approval, extract {slug}-checklist.yaml from {slug}-design.md for use in the next two phases. Trigger scenarios: "Start designing the solution", "Write design doc", "Prepare to implement XX", with the prerequisite that you already know what to do, who it's for, and how to define success.
Onboard a new repository or a repository with scattered documents into the easysdd system. Two paths are automatically determined: the empty repository path (no spec-like documents or easysdd/ directory in the repository) builds the skeleton from scratch; the migration path (the repository already has scattered documents or partial easysdd/ structure) first generates an audit report + migration mapping plan, which is confirmed by the user one by one before implementation. This skill only does two things: "build the skeleton" and "organize existing documents". After the skeleton is built, all sub-workflows can run directly. Trigger scenarios: the user says "Use easysdd in this project", "Build easysdd structure", "Initialize easysdd", "Migrate to easysdd".
Maintainer workflow for OpenClaw GitHub Security Advisories (GHSA). Use when Codex needs to inspect, patch, validate, or publish a repo advisory, verify private-fork state, prepare advisory Markdown or JSON payloads safely, handle GHSA API-specific publish constraints, or confirm advisory publish success.