Loading...
Loading...
Found 8,760 Skills
Canonical ticket lifecycle engine for multi-agent orchestration. Two backends: (1) filesystem YAML bundles for project-level work management (roadmap → bundle → tickets → review), (2) DB-backed durable tickets for session-level claim/block/close lifecycle. This skill is the single source of truth for all ticket operations.
Select an installation method, install NocoBase, and start it locally or on a server. Use when users ask how to install NocoBase, initialize a project, or start a running instance.
Set up and run competitive intelligence monitoring. Discover competitors via user input, lookalike search, web research, or G2/review sites, then create an Extruct company table with research columns for blog, social media, news, key people, and business model tracking. Re-run columns to refresh monitoring data. Triggers on: "competitor monitoring", "track competitors", "competitive intelligence", "monitor competitors", "competitor analysis", "competitive landscape", "who are my competitors", "competitor tracking".
Generate AGENTS.md file and docs/ knowledge base skeleton in the project root directory, and establish a document governance system for agent-first repositories. Manually triggered, writes the template after checking for existence.
Request or contribute a new sales/marketing/GTM skill that doesn't exist yet. Use when no existing skill covers the user's need — helps them build the skill and submit a PR, or file an issue requesting it. Also use when the user says 'there should be a skill for this', 'can we make a skill', 'I want to contribute a skill', or 'none of the sales skills cover my use case'.
Activates when users start a new novel project - guides them through the seven-step methodology (constitution → specify → clarify → plan → tasks → write → analyze) with gentle prompts and explanations
Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"
Use Claude Code to simplify the current pull request by safely reducing unnecessary scope, complexity, and noise while preserving the intended outcome.
Run Gemini CLI review against the current branch, fix only the review comments that are still valid for the current codebase, and leave invalid comments unchanged.
Use after the final approved execution scope is complete, or when the user asks whether a feature is done, ready to ship, safe to merge, or needs a quality check. Runs the post-execution quality gate: specialist review, artifact verification, and human UAT against locked decisions and the final exit state. Use for prompts like "review this feature", "is this done?", "can we ship this?", "double-check the implementation", or "run UAT".
Discover Harbor capabilities, inspect capability details, and explain grant or secret blockers before execution. Use when asked what Harbor can do, list capabilities, inspect a capability, check whether a capability exists, or find the next safe Harbor action.