jeremylongshore/tons-of-skills-marketplace

brand-strategy

Build or review a seven-part brand strategy covering identity, audience, positioning, messaging, visual principles, channels and measurement.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill brand-strategy

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

Brand Strategy Framework

Overview

Build a usable brand strategy from the creator's context and evidence. Support a full strategy, one selected phase, or a review of an existing document.

Prerequisites

  • The brand or product, intended audience and requested decision or deliverable.
  • Existing briefs, customer observations, positioning and constraints when available.
  • A selected project directory and output path for saved work. No branding API,

CLI installation or authentication is required for this document workflow.

Read the files the user selects. Reuse known answers and approvals; ask only for missing decisions that affect the requested work. If file paths are unavailable, work from supplied text and record that limitation. Do not search unrelated private documents for customer data.

Instructions

  1. Confirm the mode: full strategy, selected phase, or review. A full strategy

normally follows the seven phases in order; a focused task can use established upstream decisions without repeating discovery.

  1. Read the seven-phase framework for the

relevant questions and outputs. Preserve useful existing decisions and identify material contradictions before drafting dependent messaging or channel plans.

  1. Separate supplied facts, observed research, creator decisions and hypotheses.

Attach source paths or supplied URLs to claims about audiences, competitors or performance. If current research is unavailable, label proposed positioning and audience archetypes as hypotheses; do not invent customer quotes, competitor capabilities, market demand or cultural trends.

  1. Develop concrete choices with rationale and tradeoffs. Tie proof points to real

evidence. Treat visual directions as principles, not completed design assets; distinguish a proposed channel experiment from a proven acquisition channel.

  1. Review each requested phase against its purpose. Ask about material unresolved

choices; preserve any approval already given. Record draft/proposed/approved accurately, and never treat a generated suggestion as stakeholder approval.

  1. Write the requested document to the selected output path. For a new strategy,

suggest brand-strategy-{brand-slug}.md; use an explicitly selected existing path for revisions. Check an existing file before replacing it. Use Edit for a scoped revision, preserving unrelated sections and the creator's chosen voice.

  1. Report the saved path, sections completed, unresolved decisions and next useful

action. A partial phase deliverable must identify deferred phases rather than implying that the whole strategy is complete.

Output

A full strategy document contains an executive summary plus these seven sections:

PhaseUseful artifact
Brand TruthReason for being, core belief and values with concrete implications
Audience ArchitectureMotivations, needs, exclusions and evidence status for audience segments
Cultural ContextPositioning, alternatives and a qualified competitive landscape
Messaging FrameworkCore claim, supported proof points, objections and language guidance
Visual LanguageVisual principles and reference directions with rationale
Channel StrategyPriorities, role, themes and feasible cadence for each selected channel
Measurement FrameworkOutcome, metric definition, data source, owner and review cadence

Include scope, source inputs, decision status and open questions. A review can instead report findings by section, supporting evidence and proposed revisions. For measurement, record the actual baseline and observation window when known; otherwise write unknown. Label targets as proposed or owner-approved, and explain what evidence would test them. Do not promise that a leading indicator predicts revenue or that a strategy will deliver a specific growth rate.

Error Handling

SituationRecovery
Brand or audience is unclearAsk for the decision needed to scope the work; avoid a generic seven-section filler document.
Sources contradict a desired claimShow the conflict and revise the claim or flag missing evidence.
No customer or competitor researchDraft testable hypotheses and a bounded research plan; label the limits.
Baseline or attribution is unavailableRecord unknown and specify how it could be measured.
Output path belongs to another brandSelect a separate path or obtain an explicit revision instruction.
Earlier phases are unfinishedComplete the requested phase with assumptions listed and flag dependent decisions.

Examples

Full strategy: "Build a strategy for our coffee subscription using this brief." Read the brief, reuse supplied audience and pricing decisions, then develop the seven phases. Save a draft with unsupported taste or demand assumptions labeled.

Focused phase: "Revise messaging in brand-strategy-coffee.md for office buyers." Read that document and relevant audience evidence. Edit messaging and identify any positioning or channel implications without silently rewriting the strategy.

Review: "Our deck says awareness doubled, but we have no baseline." Flag the unsupported result, keep the metric unknown, and propose a measurement window and data source instead of inventing a prior value.

Resources

같은 저장소의 Skills

더 많은 Skills

모든 Skills
jeremylongshore
커뮤니티

agent-context-loader

'Execute proactive auto-loading: automatically detects and loads agents.md files. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose. '

1시간 설치 수
2
GitHub Stars
2.9천
업데이트
11월 8일
jeremylongshore
커뮤니티

agent-creator

'Create production-grade agent .md files aligned with the current Anthropic subagent contract. Also validates existing agents against the marketplace compliance rules. Use when building custom subagents, reviewing agent quality, or creating parallel agent architectures for orchestrator skills. Trigger with "/agent-creator", "create an agent", "build a subagent", or "validate my agent". Make sure to use this skill whenever creating agents/.md files for plugins or standalone use. '

1시간 설치 수
2
GitHub Stars
2.9천
업데이트
11월 8일
jeremylongshore
커뮤니티

agent-patterns

'Execute this skill should be used when the user asks about "SPAWN REQUEST format", "agent reports", "agent coordination", "parallel agents", "report format", "agent communication", or needs to understand how agents coordinate within the sprint system. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose. '

1시간 설치 수
2
GitHub Stars
2.9천
업데이트
11월 8일
jeremylongshore
커뮤니티

agent-safety-preflight

Generate a local repository risk receipt before Claude Code or other AI-agent edits. Use when the user asks to prepare a repository for agent changes, check for risky hooks or credential-writing automation, or run the /agent-preflight command. Trigger with "run agent preflight", "check this repo before agent edits", or "/agent-preflight".

1시간 설치 수
2
GitHub Stars
2.9천
업데이트
11월 8일