Loading...
Loading...
Found 5,608 Skills
CalendarHero integration. Manage Persons, Meetings. Use when the user wants to interact with CalendarHero data.
Manage editorial content pipeline through 6 stages: Ideas, Outlined, Drafted, Editing, Ready, Published. Use when user wants to view pipeline status, add ideas, move content between stages, schedule posts, or archive published content. Use for "content calendar", "pipeline status", "add idea", "schedule post", or "move to drafted". Do NOT use for creating Hugo content files, deploying posts, or modifying site configuration.
Agent skill for performance-analyzer - invoke with $agent-performance-analyzer
Salesforce Data Cloud Segment phase. TRIGGER when: user creates or publishes segments, manages calculated insights, inspects segment counts or membership, or troubleshoots audience SQL in Data Cloud. DO NOT TRIGGER when: the task is DMO/mapping/identity-resolution work (use sf-datacloud-harmonize), activation work (use sf-datacloud-act), query/search-index work (use sf-datacloud-retrieve), or STDM/session tracing (use sf-ai-agentforce-observability).
Agent skill for github-modes - invoke with $agent-github-modes
Use when reviewing pending todos for approval, prioritizing code review findings, or interactively categorizing work items
Liondesk integration. Manage Leads, Persons, Organizations, Deals, Pipelines, Activities and more. Use when the user wants to interact with Liondesk data.
Weclapp integration. Manage Organizations. Use when the user wants to interact with Weclapp data.
Edit an existing PRD. Use when the user says "edit this PRD".
Automatically create a PR to register insights, conventions, and best practices obtained from the current project as rules in the TBSten/skills repository. It runs the entire end-to-end process: collecting insights from the project's CLAUDE.md, .claude/rules/ directory and codebase, packaging them as reusable Claude Code rules, and creating the PR. Rules are files stored in .claude/rules/, and unlike skills, they do not require frontmatter. RULE.md serves as the main rule body, while detailed documentation (<rule-name>.md / <rule-name>.ja.md) is placed directly under the rules/ directory. Use when the user requests: "Register insights as rules", "contribute rule", "Share this rule", "Register as a rule", "Compile rules into a PR", "Turn this convention into a rule", "Turn best practices into rules". gh CLI and git must be installed.
Use after exploring completes or whenever a feature already has locked requirements and now needs research, synthesis, phase definition, story mapping, and executable task beads. Use for prompts like "plan this", "break this into tasks", "decompose this work", "map the stories", "research and plan", or "turn this into beads" before implementation begins.
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.