home/categories/business
domain cluster

Business

Tools for enterprise, finance, and management.

14022 skillsall categories
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
project-management
4

issue-classifier

Classify work type from issue metadata (CLI not yet available)

fractary
fractary
business
open
real-estate-legal
4

standard

Standard rules to comply with. Agents must always use this skill.

ZeroAurora
ZeroAurora
business
open
real-estate-legal
4

bsblan-parameters

Add new BSB-LAN parameters to the python-bsblan library. Use this skill when adding parameter IDs, updating models, or extending the API to support new heating controller parameters.

liudger
liudger
business
open
real-estate-legal
4

openspec-archiving-cn

归档已完成的变更并将规范差异合并到常驻文档。用于变更已部署、准备归档或实施后需要更新规范时。触发词包括 "openspec归档", "归档", "归档提案", "合并规范", "完成提案", "更新文档", "定稿规范", "标记完成"。

forztf
forztf
business
open
real-estate-legal
4

privacy-compliance

GDPR, CCPA, and privacy compliance guidance for data protection. Use when handling personal data, implementing consent management, or ensuring regulatory compliance across jurisdictions.

jpoutrin
jpoutrin
business
open
real-estate-legal
4

privacy

Privacy and data protection - GDPR, CCPA, consent. Use when handling user data.

SylphxAI
SylphxAI
business
open
sales-marketing
4

avoiding-ambiguous-suffixes

命名・設計レビューにおいて、Manager / Util / Facade / Service / Runtime / Engine など 意味が一意に定まらないサフィックスの使用を検出し、責務・境界・契約が明確に伝わる命名へ導く。 トリガー:「この命名で良いか」「Manager という名前を使いたい」「命名レビューして」 「サフィックスの選び方」といった命名相談で起動。

j5ik2o
j5ik2o
business
open
sales-marketing
4

pm-coach

Coaches product managers on skill development, career growth, and PM craft. Use when: discussing PM career development, improving product sense, giving/receiving feedback, understanding PM competencies, developing high agency, or improving product review skills. Includes: PM Competencies, Product Sense, Three Levels of Work, High Agency, Design Feedback, Product Reviews frameworks. Sources: Ravi Mehta, Julie Zhuo, Shreyas Doshi, Ami Vora.

qingxuantang
qingxuantang
business
open
sales-marketing
4

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

EricOo0
EricOo0
business
open
sales-marketing
4

ui-density

Analyze and improve UI density using Matt Ström's 4-dimensional framework. Use when interfaces feel too sparse, too cluttered, or when users complain about efficiency.

rohunvora
rohunvora
business
open
sales-marketing
4

ui-refactor

Tactical user interface design guide for fixing layouts, selecting colors/fonts, and creating professional UIs. Use when the user asks to "make this look better," needs help with CSS/styling decisions, wants to create a design system, or needs to fix a cluttered interface.

LovroPodobnik
LovroPodobnik
business
open
sales-marketing
4

uiux

UI/UX - design system, accessibility. Use when building interfaces.

SylphxAI
SylphxAI
business
open
sales-marketing
4

pricing

Pricing strategy - tiers, feature gating. Use when designing pricing.

SylphxAI
SylphxAI
business
open
sales-marketing
4

requirements-documentation

要件ドキュメントの作成・構造化・品質管理・ハンドオフを支援するスキル。 カール・ウィーガーズの要求工学理論に基づき、ステークホルダーと開発チームの双方に有用な仕様書を作成する。 Anchors: • Software Requirements (Karl Wiegers) / 適用: 要件管理全般 / 目的: 明確で検証可能な仕様 • IEEE 830 SRS Standard / 適用: ドキュメント構造 / 目的: 標準準拠の仕様書 • Don't Make Me Think (Steve Krug) / 適用: 情報設計 / 目的: 読みやすいドキュメント Trigger: Use when creating requirements documents, writing specifications, preparing stakeholder reviews, or establishing requirements traceability. requirements document, specification, SRS, stakeholder review, traceability matrix, 要件定義書, 仕様書

daishiman
daishiman
business
open
sales-marketing
4

strategy-advisor

Helps with product and business strategy using proven frameworks. Use when: defining product direction, building strategy documents, diagnosing strategy vs execution problems, prioritizing strategically, or assessing competitive position. Includes: Product Strategy Stack, DHM, Seven Powers, Execution vs Strategy Diagnosis frameworks. Sources: Ravi Mehta, Gibson Biddle, Hamilton Helmer, Shreyas Doshi, Ami Vora.

qingxuantang
qingxuantang
business
open
sales-marketing
4

information-architecture

ユーザーが必要な情報を素早く見つけられるドキュメント構造設計スキル。 階層設計、ナビゲーション、情報粒度管理の技術を提供。 Anchors: • Information Architecture (Rosenfeld, Morville) / 適用: IA設計原則 / 目的: ユーザー中心の構造設計 • Don't Make Me Think (Steve Krug) / 適用: ナビゲーション設計 / 目的: 直感的な情報探索 • Clean Architecture (Robert C. Martin) / 適用: 依存関係ルール / 目的: 保守可能な構造 Trigger: Use when designing document structures, creating navigation systems, organizing content hierarchies, building documentation sites, or planning information granularity. documentation, structure, navigation, hierarchy, sitemap, content organization

daishiman
daishiman
business
open
sales-marketing
4

openspec-proposal-creation-cn

通过openspec规范驱动的方法创建结构化的变更提案与规范差异。用于规划功能、创建提案、编写规范、引入新能力或启动开发流程。触发词包括 "openspec提案", "规划", "创建提案", "规划变更", "规范功能", "新功能", "新特性", "新需求", "添加功能规划", "设计规范"。

forztf
forztf
business
open
sales-marketing
4

agent-quality-standards

エージェント品質基準と検証プロセスを専門とするスキル。エージェント設計、品質メトリクス、検証戦略、エラーハンドリング、品質スコアリングに対応。 Anchors: • The Pragmatic Programmer (Andrew Hunt, David Thomas) / 適用: エージェント品質設計 / 目的: 実践的な品質基準の構築 • Code Complete (Steve McConnell) / 適用: エラーハンドリング戦略 / 目的: 堅牢なエージェント実装 Trigger: Use when evaluating agent quality, designing completion criteria, defining quality metrics, or planning error handling strategies.

daishiman
daishiman
business
open
sales-marketing
4

customer-feedback-framework

Comprehensive customer feedback framework including NPS, CSAT, CES surveys, exit interviews, user research, feature request management with RICE prioritization, feedback analysis, close-the-loop processes, and 90-day implementation roadmap for Voice of Customer programs

maigentic
maigentic
business
open
sales-marketing
4

idea-honing

Clarify feature ideas through iterative Q&A, recording insights to guide concept development

cbgbt
cbgbt
business
open
sales-marketing
4

use-case-modeling

ユースケース駆動の要件分析スキル。 ユーザーとシステムの対話を構造化し、ビジネスロジックを明確にします。 アクター識別から詳細シナリオ設計まで段階的に進めます。 Anchors: • 『Writing Effective Use Cases』(Alistair Cockburn) / 適用: ユースケース設計 / 目的: 要件仕様の明確化 • 『The Pragmatic Programmer』(David Thomas, Andrew Hunt) / 適用: 要件分析 / 目的: 実践的な品質維持 Trigger: ユースケースモデリング、アクター分析、システム要件定義時に使用

daishiman
daishiman
business
open
sales-marketing
4

design-concepts

Creates conceptual designs that illustrate design strategy and approach. Leverages research insights and design briefs to develop UI concepts, mood boards, and interactive prototypes. Translates strategic direction into visual design explorations that communicate intent and gather feedback.

mevans2120
mevans2120
business
open
sales-marketing
4

interview

Interview user with targeted questions to clarify requirements. Use this BEFORE starting any implementation when instructions are vague or lack detail.

d-issy
d-issy
business
open
Previous
Page 353 / 585
Next