Plan advisory firms. TRIGGERS - Use when user needs help with advisory-firm-plan related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
527 件 ・ 関連度順
概要と使いどころ
Plan advisory firms. TRIGGERS - Use when user needs help with advisory-firm-plan related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when gathering, structuring, and documenting requirements for a Financial Services Cloud (FSC) wealth management implementation — including financial planning workflow discovery, portfolio review process mapping, client lifecycle requirements, advisor tooling needs, and FSC architecture determination (managed package vs. FSC Core). Trigger keywords: wealth management requirements, FSC requirements gathering, financial planning workflow, portfolio review process, advisor tools setup, FSC data model scoping, wealth management process mapping. NOT for implementation, configuration, or code — use financial-account-setup, fsc-action-plans, or apex/fsc-financial-calculations for those. NOT for FSC architecture decisions — use architect/wealth-management-architecture. NOT for Health Cloud or NPSP requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Design, implement, or audit a Change Advisory Board (CAB) process for Salesforce deployments: change classification (standard, normal, emergency), required approvals, deployment gate sequencing, and integration with external ITSM tooling. NOT for scoring how risky one release is - use admin/deployment-risk-assessment. NOT for executing or troubleshooting the deployment itself - use admin/change-management-and-deployment. Also covers: the CAB charter (membership, quorum, decision rights), the CAB decision record artefact and its linter, the change classification matrix, the deployOptions a CAB decision pins (checkOnly, testLevel, rollbackOnError, ignoreWarnings, runTests), the 10-day quick-deploy validity window, the deploy-window vs freeze-register check, and the emergency (ECAB) path with its mandatory retrospective.
日本語の概要は準備中です。原文の説明を表示しています。
Run the Advisory Council — a multi-perspective market analysis that spawns 5 AI advisors (The Skeptic, The Macro Bull, The Risk Manager, The Technical Analyst, The Contrarian) powered by MiniMax M2...
日本語の概要は準備中です。原文の説明を表示しています。
name: advisory-committee description: "4-agent AI advisory committee for strategic decisions. Runs CS, Marketing, Finance, and Tech agents in sequence to analyze proposals and deliver a majority-vo...
日本語の概要は準備中です。原文の説明を表示しています。
Spin up a single agent as an advisor — second opinion on the current task. Use when the user says "advisor", "second opinion", "what does X think", or wants an outside take without delegating the work itself.
日本語の概要は準備中です。原文の説明を表示しています。
Provide private local advice to Codex about whether to call a tool, which candidate is best, risk, recovery, and task completion. Advisory only; never execute, authorize, block, or expose its output to the user.
日本語の概要は準備中です。原文の説明を表示しています。
Kontokonzept für den budgetierten Einsatz teurer oder knapper Modelle (Advisor, Reviewer, Spezialmodelle, Dauer-Worker) in längeren Agentenläufen. Beginnt mit einer gemeinsamen Aushandlung zwischen Nutzer und Modell über verfügbare Modelle, Rollen und Kontingente je Zeitfenster, führt ein Konto über jeden Einsatz, setzt vor jeder Eskalation ein Puzzleteil-Vorverfahren und erlaubt Anpassungen mitten im Lauf. Verwenden bei "Budget", "Kontingent", "Konto führen", "nur einmal pro Stunde", "Reviewer sparsam einsetzen", "Fable/Codex/Sol/Astra/Luna/Advisor nur begrenzt", "/budgetierung", und immer dann, wenn ein Operator-, Forschungs- oder Automationslauf mehrere Modelle mit unterschiedlichen Kosten kombinieren soll — auch wenn der Nutzer das Wort Budget nicht nennt, aber Einsatzgrenzen für Modelle vorgibt.
日本語の概要は準備中です。原文の説明を表示しています。
Cursorで任意のリファクタリング改善案を返すnative入口。共有refactor-advisorとrefactor-guidanceを読み、reviewerのVERDICTから分離する。
ローカルの差分・ファイルを対象に、機能要件とは別のリファクタリング提案を出す。レビューの完了阻害判定とは分け、保守性の改善候補を必要な場合だけ扱う。ユーザーが /refactor-advisor と入力したら使う。
Kelly Insurance Intel: App-in-Skill daily industry intelligence cockpit for insurance and wealth advisory (Busabase App-in-Skill). Use when the user asks about insurance, wealth advisory, client risk reminders, market news, policyholder follow-up,保险, or financial-advisor sales scenes. Prepares news/source signals, buyer-intent interpretation, approved sales actions, and channel drafts for review before any external handoff.
日本語の概要は準備中です。原文の説明を表示しています。
Design AI financial advisory assistants. TRIGGERS - Use when user needs help with ai-financial-advisor related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Write advisor agreements. TRIGGERS - Use when user needs help with advisor-agreement related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Design advisory boards. TRIGGERS - Use when user needs help with advisory-board-design related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Plan advisory firms. TRIGGERS - Use when user needs help with advisory-firm-plan related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Plan advisory services for accounting firms. TRIGGERS - Use when user needs help with advisory-services-plan related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
OpenClawの脆弱性報告を、公開済みのバージョンと信頼範囲の根拠で確認し、終了・継続・影響の絞り込みを判断して、管理者向けの返信案をまとめます。
Use when a task is too large for one model pass, needs parallel research or generation across many subtasks (like researching a dozen competitors at once), or the user asks to orchestrate multiple models, split work across a model team, run an advisor-worker loop, have a stronger model review the plan while cheap workers execute, or says "too big for one model" or "fan this out". Not for single-file edits or tasks one model handles in one pass.
日本語の概要は準備中です。原文の説明を表示しています。
Proactive "make the most of gbrain" coaching. Runs `gbrain advisor` on a cadence and pings the user with the top high-leverage actions for their brain: version drift, pending migrations, stalled jobs, low embed coverage, setup smells, and uninstalled brain skills. Read-only; always asks before fixing.
日本語の概要は準備中です。原文の説明を表示しています。
/cs:founder-mode <question> — Auto-routes any founder question to the right C-role advisor or to /cs:boardroom for multi-role topics. The single-command entry point. Use when a founder asks any strategic question without knowing which advisor or command fits — e.g. 'runway pressure' routes to the CFO, 'gross retention dropped' routes to the CCO.
日本語の概要は準備中です。原文の説明を表示しています。
General Counsel advisory for startups: contract review (MSA, SaaS, NDA, DPA, employment), IP strategy, term sheet decoding, and regulatory landscape mapping. Use when reviewing any contract or term sheet, deciding when to engage outside counsel, defining IP strategy, evaluating regulatory exposure (HIPAA, GDPR, FDA, fintech), or when user mentions general counsel, GC, legal review, contract risk, term sheet, IP assignment, or regulatory exposure. NOT a substitute for licensed counsel — surfaces questions to bring to qualified attorneys.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building a quarterly bookings forecast, ARR projection, pipeline forecast, NRR projection, or commit/best-case/pipe-only board number — especially when the CRO needs to walk the board through funnel math + cohort ARR + per-stage conversion assumptions without the theatre of a single undefended number. Decomposes pipeline into commit, best-case, and pipe-only tiers; projects cohort-level NRR/GRR to surface leaky cohorts before they show up in the consolidated number; scores per-stage funnel confidence so soft-floor stages get treated differently from high-confidence ones. Every output explicitly names the conversion rate used, the data window, and the weighting choice. For Head of Commercial, RevOps, VP Sales, and CRO at quarterly forecast or board prep. NOT financial close (see finance/financial-analysis). NOT strategic CRO hiring/territory (see c-level-advisor/cro-advisor). NOT pricing (see sibling pricing-strategist).
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing, approving, or designing commercial motion — pricing models, deal review, discount approval, partnership economics, channel mix, commercial policy, RFP/RFI response, bookings forecast. Triggers on "review this deal", "should we discount", "pricing model", "partner economics", "RFP response", "bookings forecast", "channel mix". Forks context to route to one of seven Commercial sub-skills (pricing-strategist, deal-desk, partnerships-architect, channel-economics, commercial-policy, rfp-responder, commercial-forecaster) and returns a digest. Distinct from business-growth (sales execution) and c-level-advisor/cro-advisor (strategic CRO judgment).
日本語の概要は準備中です。原文の説明を表示しています。
VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and production discipline (on-call, deployment cadence, postmortem culture). Use when sprint velocity is dropping, eng hiring is broken, team structure is unclear, or deciding when to add a tech-lead manager. NOT a CTO skill (which owns architecture) — VPE owns delivery operations and how the team ships.
日本語の概要は準備中です。原文の説明を表示しています。