Loading...
Loading...
Found 5,651 Skills
Qwilr integration. Manage Accounts. Use when the user wants to interact with Qwilr data.
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".
Write or update external guide documents for the project —— dev-guide (for contributors / integrators / downstream developers) and user-guide (for end users). The output is stored in the project's docs/ directory, maintained alongside the code, and searchable by search tools. Difference from libdoc: guidedoc is task-oriented ("How to do Y with X"), while libdoc is reference-oriented ("What each part of X looks like"). Trigger scenarios: When the user says "write documentation", "developer guide", "user guide", or proactively push when feature-acceptance is completed.
Use when batch-resolving approved todos, especially after code review or triage sessions
Shows a structured progress dashboard for an album with percentage complete per phase, blocking items, and status breakdown. Use for a quick visual overview of album progress.
Propose a change with optional working artifacts. Use when the user wants a structured proposal with design notes, tasks, and a clear path to implementation.
Kadoa integration. Manage Leads, Persons, Organizations, Deals, Projects, Activities and more. Use when the user wants to interact with Kadoa data.
8x8 integration. Manage Persons, Organizations, Deals, Leads, Activities, Notes and more. Use when the user wants to interact with 8x8 data.
When developing new features, follow this sub-process — take the vague idea of "add X capability" through to the acceptance closure, with solution documents archived so that both AI and users can later check the original thinking and decision rationale. Trigger scenarios are focused on adding new capabilities ("develop new feature", "add X", "implement XX"), and do not handle bugs in existing code. This skill only acts as a router, deciding which sub-skill to trigger next among brainstorm / design / fastforward / implement / acceptance based on existing artifacts.
One-stop skill for the project architecture center — draft new architecture documents, refresh existing ones, or conduct an architecture health check. Automatically determine the mode based on user input: `new` (draft)/ `update` (refresh to latest code status)/ `check` (review without modification, generate issue list). The `check` mode has three sub-objectives: consistency within a single feature design, alignment between design and code, and consistency among multiple documents under `codestable/architecture/`. Single-target rule — only modify one document or check one target at a time. Trigger scenarios: User says "fill in an architecture doc", "draft an architecture document", "refresh the architecture directory", "write down this module structure", "conduct an architecture check", "is the design internally consistent?", "does the plan match the code?", "are there conflicts among several documents in the architecture folder?", or when an architecture action is required before proceeding during the feature-design / feature-acceptance / implement phases.
Radar integration. Manage Organizations. Use when the user wants to interact with Radar data.
Audit design documents for missing decisions, compatibility risks, rollout gaps, and observability omissions. Use whenever the user asks to review a design doc, architecture proposal, implementation-facing design, plan, or design-adjacent markdown file for completeness, migration strategy, rollback, data handling, or suggested additions without directly editing the document. Also trigger on short requests such as `review <file>.md` or `audit <file>.md` when the target looks like a design, plan, architecture, proposal, or decision document.