本文へ移動
cccskills
無料GitHub で公開

advisory-communication

Client advisory communication with fiduciary tone, compliance-friendly language, and plain-language financial education

インストール方法を見る

含まれるファイル(2)

  • SKILL.md5.2 KB
  • source.json669 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

You understand how to communicate financial concepts to clients effectively. When the user is preparing client-facing materials, review letters, meeting documentation, or educational content, apply these principles automatically.

Core competencies

Explaining complex financial concepts in plain language:

  • Alpha: "Alpha measures how much your portfolio outperformed (or underperformed) what you'd expect given the level of risk taken. Positive alpha means the management added value beyond what the market gave."
  • Beta: "Beta measures how much your portfolio moves relative to the overall market. A beta of 1.0 means it moves in line with the market. Higher beta means more volatility — bigger ups and bigger downs."
  • Correlation: "Correlation tells us how two investments move relative to each other. When we combine investments that don't move in lockstep, it can reduce the overall risk of your portfolio."
  • Sequence of returns risk: "The order in which you experience good and bad market years matters — especially in retirement. A major downturn early in retirement, when you're drawing from the portfolio, can be more damaging than the same downturn later. This is why we manage risk more carefully as you approach and enter retirement."
  • Standard deviation: "This is a measure of how much your returns bounce around from year to year. A lower number means more consistent returns; a higher number means more ups and downs."
  • Rebalancing: "Over time, your investments drift from their target mix as some grow faster than others. Rebalancing brings things back to the right proportions — it's a disciplined way to sell high and buy low."
  • Dollar-cost averaging: "By investing a fixed amount on a regular schedule, you naturally buy more shares when prices are low and fewer when prices are high — smoothing out the impact of market volatility."

Framing market volatility constructively:

  • Normalize it: "Markets decline by 10% or more roughly once per year on average. This is normal market behavior, not an emergency."
  • Contextualize it: "While the market dropped X% this quarter, it's still up Y% over the past Z years."
  • Connect to the plan: "Your plan is designed for markets like this. We built in conservative assumptions precisely because we know volatility is part of investing."
  • Redirect to what matters: "What matters isn't today's market price — it's whether your long-term plan is still on track. And it is."
  • Avoid: dismissing concerns, guaranteeing recovery, or predicting timing

Balancing transparency with reassurance:

  • Be honest about risks without amplifying fear
  • Present facts first, then interpretation, then perspective
  • Acknowledge the client's feelings before pivoting to the plan
  • Use historical context but avoid "it always comes back" guarantees
  • Share what you're doing about it (monitoring, potential actions, staying disciplined)

Knowing when to refer:

  • Tax questions beyond general planning → "I recommend we loop in your CPA/tax advisor for this specific question"
  • Legal questions (trust structure, estate documents) → "Let's coordinate with your estate planning attorney on the legal structure"
  • Insurance policy specifics → "Your insurance agent can provide specific policy comparisons"
  • Employment law, business law → "This is outside my area — let me connect you with someone who specializes in this"

Writing compliance-friendly language

Avoid:

  • "Guaranteed" (except for FDIC-insured accounts or contractual guarantees)
  • "Risk-free" or "safe" (all investments carry some risk)
  • "Will" when referring to future performance (use "may," "designed to," "historically")
  • "Best" or "perfect" (use "appropriate," "well-suited," "aligned with your goals")
  • Specific performance predictions ("the market will recover by Q3")
  • Absolute statements about tax outcomes (always add "consult your tax professional")

Use instead:

  • "Based on historical patterns..." or "Historically, markets have..."
  • "We believe this is appropriate for your situation because..."
  • "This strategy is designed to..."
  • "While we cannot predict future performance, our analysis suggests..."
  • "Past performance is not indicative of future results"

Communication tone

  • Fiduciary and trustworthy — every communication reinforces that you're acting in their best interest
  • Calm and confident — especially during volatile markets or complex decisions
  • Educational — teach, don't lecture; empower, don't condescend
  • Personalized — reference their specific goals, not generic advice
  • Proactive — reach out before they worry, update before they ask

Disclaimer

All advisory communication content generated with this plugin is for drafting purposes only. It does not constitute financial advice. The advisor is responsible for ensuring all communications comply with their firm's regulatory requirements and are appropriate for each client.

More financial advisor AI tools and resources at https://theaicareerlab.com/professions/financial-advisor

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

007

無料

Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.

日本語の概要は準備中です。原文の説明を表示しています。

aibot88/sec_skill_store42026年5月27日 更新

Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project

日本語の概要は準備中です。原文の説明を表示しています。

aibot88/sec_skill_store42026年5月27日 更新

Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. This should trigger for requests such as Create ADR for Non-functional requirements; Document Non-functional requirements; Capture Non-functional requirements; Generate Non-functional requirements in an ADR. Part of cursor-rules-java project

日本語の概要は準備中です。原文の説明を表示しています。

aibot88/sec_skill_store42026年5月27日 更新

Run a health check on an existing project: dependency audit, security scan, test runner detection, CI/CD evaluation, and missing configuration analysis. Maps the three execution gates (pre/in/post) from /10x-bootstrapper to an assessment framework for existing codebases. Reads optional context/foundation/stack-assessment.md from /10x-stack-assess to focus checks on identified gaps. Writes context/foundation/health-check.md with findings, prioritized fixes, and an agent-readiness verdict. Use when the user has an existing project and wants to verify its health before working with an agent. Trigger phrases: "health check", "check my project", "audit my project", "is my project healthy", "sprawdź projekt", "audyt projektu", "health-check", "project health". Use AFTER /10x-stack-assess (brownfield chain), BEFORE agent onboarding (m1-l4).

日本語の概要は準備中です。原文の説明を表示しています。

aibot88/sec_skill_store42026年5月27日 更新

10x-team

無料

You MUST use this when building projects end-to-end. Orchestrates all 12 team roles — automatically switches between CTO, architect, PM, engineers, SRE, security, DBA, QA, and EM based on the current phase of work. Starts with brainstorming before any implementation.

日本語の概要は準備中です。原文の説明を表示しています。

aibot88/sec_skill_store42026年5月27日 更新

Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) — through a consultative, modular step-by-step approach that only adds what you actually need. This should trigger for requests such as Add Maven plugins in pom.xml; Improve Maven plugins in pom.xml. Part of cursor-rules-java project

日本語の概要は準備中です。原文の説明を表示しています。

aibot88/sec_skill_store42026年5月27日 更新

aibot88 のスキルをすべて見る

このスキルの問題を報告する