Loading...
Loading...
Found 8,194 Skills
Infobip integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Infobip data.
Use before building anything new or when a plan needs review. Not for bug fixes or small edits.
Use when researching an unfamiliar domain or preparing a research article. Not for quick lookups or single-file reads.
Webhook integration. Manage Recordses. Use when the user wants to interact with Webhook data.
Commit unstaged changes, push changes, submit a pull request.
Document codebase as-is with research directory for historical context
Run an interactive naming session for a project. Use when the user wants to name a project, app, package, tool, or repo. Presents names in rounds, tracks preferences, and refines suggestions based on selections.
Elevate a project-local skill to the shared ai-skills repo. Use when you want a project skill available in other repos.
Obtain and refresh JWT access tokens, and manage API keys for the Spuree V1 API
Draft or update architecture documents under `easysdd/architecture/` — describe what a subsystem/module looks like currently, how it is divided, and how external interfaces operate, to provide pre-positioning input for subsequent feature-design. Information sources include code + user materials (oral accounts, scattered documents, compound deposits, existing decisions), and the output can be reverse-validated by anchoring to specific `file:line`. Two modes: new (draft a new architecture document from scratch), update (refresh an existing document based on the latest code status and new user materials). Single-target rule — only modify one document at a time. Trigger scenarios: user says "fill in an architecture doc", "draft an architecture document", "update the architecture directory", "write down the structure of this module", or when it is found that "something that should be in the architecture is missing" during the feature-design / feature-acceptance phase.
Conduct an architecture health check on a design — either verify if the design is internally consistent (no conflicts between terminology, contracts, and implementation steps) or check if the design aligns with the code (ensuring what was promised in the design is actually implemented in code). This skill only outputs issue lists and repair suggestions, and does not make any modifications. It focuses on only one target each time; "顺手把另一项也查了" is not allowed. Trigger scenarios: Users say "perform architecture check", "is the design internally consistent?", "does the plan align with the code?", or want to conduct a health check before proceeding to the implement/acceptance phase.
Manage a team's tasks and use Box as the file storage backend