../../../c-level-advisor/strategic-alignment/SKILL.md

25 stars

Best use case

../../../c-level-advisor/strategic-alignment/SKILL.md is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Teams using ../../../c-level-advisor/strategic-alignment/SKILL.md should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/strategic-alignment/SKILL.md --create-dirs "https://raw.githubusercontent.com/ComeOnOliver/skillshub/main/skills/alirezarezvani/claude-skills/strategic-alignment/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/strategic-alignment/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How ../../../c-level-advisor/strategic-alignment/SKILL.md Compares

Feature / Agent../../../c-level-advisor/strategic-alignment/SKILL.mdStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

This skill provides specific capabilities for your AI agent. See the About section for full details.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

../../../c-level-advisor/strategic-alignment/SKILL.md

Related Skills

strategic-clarity

25
from ComeOnOliver/skillshub

Guided workflow for establishing team identity, boundaries, and strategic clarity. Use when starting a new role, inheriting ambiguity, when a team lacks clear identity, or when you need to define "what we own" vs "what we don't". Triggers include "strategic clarity", "team identity", "new role", "inherited ambiguity", "what does my team own", or "define our boundaries".

../../../c-level-advisor/scenario-war-room/SKILL.md

25
from ComeOnOliver/skillshub

No description provided.

../../../c-level-advisor/executive-mentor/skills/postmortem/SKILL.md

25
from ComeOnOliver/skillshub

No description provided.

../../../c-level-advisor/org-health-diagnostic/SKILL.md

25
from ComeOnOliver/skillshub

No description provided.

../../../c-level-advisor/internal-narrative/SKILL.md

25
from ComeOnOliver/skillshub

No description provided.

../../../c-level-advisor/executive-mentor/skills/hard-call/SKILL.md

25
from ComeOnOliver/skillshub

No description provided.

../../../c-level-advisor/executive-mentor/SKILL.md

25
from ComeOnOliver/skillshub

No description provided.

../../../c-level-advisor/culture-architect/SKILL.md

25
from ComeOnOliver/skillshub

No description provided.

cro-advisor

25
from ComeOnOliver/skillshub

Revenue leadership for B2B SaaS companies. Revenue forecasting, sales model design, pricing strategy, net revenue retention, and sales team scaling. Use when designing the revenue engine, setting quotas, modeling NRR, evaluating pricing, building board forecasts, or when user mentions CRO, chief revenue officer, revenue strategy, sales model, ARR growth, NRR, expansion revenue, churn, pricing strategy, or sales capacity.

cpo-advisor

25
from ComeOnOliver/skillshub

Product leadership for scaling companies. Product vision, portfolio strategy, product-market fit, and product org design. Use when setting product vision, managing a product portfolio, measuring PMF, designing product teams, prioritizing at the portfolio level, reporting to the board on product, or when user mentions CPO, product strategy, product-market fit, product organization, portfolio prioritization, or roadmap strategy.

coo-advisor

25
from ComeOnOliver/skillshub

Operations leadership for scaling companies. Process design, OKR execution, operational cadence, and scaling playbooks. Use when designing operations, setting up OKRs, building processes, scaling teams, analyzing bottlenecks, planning operational cadence, or when user mentions COO, operations, process improvement, OKRs, scaling, operational efficiency, or execution.

../../../c-level-advisor/competitive-intel/SKILL.md

25
from ComeOnOliver/skillshub

No description provided.