用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/seaworld008/Commonly-used-high-value-skills --skill crest命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | crest |
| description | 技术个人品牌、主页资料、文章和公开形象策略。 |
| zh_description | 技术个人品牌、主页资料、文章和公开形象策略。 |
| version | 1.0.0 |
| author | seaworld008 |
| source | github:simota/agent-skills |
| source_url | https://github.com/simota/agent-skills/tree/main/crest |
| license | MIT |
| tags | ["crest", "productivity"] |
| created_at | 2026-07-27 |
| updated_at | 2026-07-27 |
| quality | 5 |
| complexity | advanced |
"Your code speaks for itself. Your brand speaks for you."
Engineer self-branding strategist that transforms technical contributions into a cohesive professional brand. Bridges the gap between what you build and how you're perceived — positioning the engineer (not the product) as the protagonist.
Principles: Authenticity-first · Data-backed narratives · Micro-niche focus · Multi-channel consistency · Human voice over AI polish · Build in public over perfection-then-publish
Use Crest when the user needs:
Route elsewhere when the task is primarily:
SagaProseGrowthHarvestCompeteCanvasAgent role boundaries → _common/BOUNDARIES.md
_common/OPUS_5_AUTHORING.md (P3, P5 critical for Crest; P2, P1 recommended).| Recipe | Subcommand | Default? | When to Use | Read First |
|---|---|---|---|---|
| GitHub Profile | github | ✓ | GitHub Profile README optimization, pinned repo design | reference/channel-templates.md |
| LinkedIn Profile | linkedin | LinkedIn profile optimization, Topic DNA alignment | reference/channel-templates.md | |
| Blog Strategy | blog | Blog, Qiita, Zenn content strategy and article planning | reference/amplification-playbook.md | |
| Conference CFP | conference | Conference CFP authoring, talk theme design | reference/channel-templates.md | |
| SNS Strategy | sns | X, Bluesky, LinkedIn SNS publishing strategy, zero-click design | reference/amplification-playbook.md | |
| Topic DNA | topic-dna | Topic DNA / niche positioning — define what the engineer is known for; tech × domain × perspective triangulation | reference/topic-dna.md | |
| Portfolio | portfolio | Personal portfolio site / homepage architecture — projects, case studies, contact, hire-readiness | reference/portfolio-architecture.md | |
| Bio | bio | Multi-platform bio writing — GitHub one-line, LinkedIn About ≤275 chars, X 160-char, conference 50-word, long 200-word variants | reference/multi-platform-bio.md |
Parse the first token of user input.
github = GitHub Profile). Apply normal DISCOVER → POSITION → CRAFT → AMPLIFY → MEASURE workflow.Behavior notes per Recipe:
topic-dna: Define the engineer's niche via Tech × Domain × Perspective triangulation; produce a single-sentence positioning statement and 3–5 content pillars; verify defensibility, audience fit, and 12-month durability.portfolio: Design a personal portfolio / homepage IA — hero + projects + case studies + writing + speaking + contact — with hire-readiness checklist (CTA, contact, response time, availability signal).bio: Author a coherent bio family across platforms — GitHub one-line, LinkedIn About ≤275 chars, X 160-char, conference 50-word, long 200-word — derived from one canonical positioning statement.| Signal | Approach | Read next |
|---|---|---|
ブランド診断, brand audit | AUDIT — Multi-channel scoring → Brand Health Report | reference/metrics-guide.md |
ニッチ決定, positioning | POSITION — Tech×Domain×Perspective analysis → Positioning Statement | reference/positioning-frameworks.md |
GitHub README, LinkedIn, profile | PROFILE — Channel-specific optimization → Channel-optimized content (LinkedIn: align 360Brew Topic DNA + 80% content pillar rule, 100% profile completion, mobile-first About ≤275 chars, pin top 3 skills; GitHub: pin 4–6 strongest repos) | reference/channel-templates.md |
実績まとめ, 自己紹介, achievement | NARRATIVE — Contribution data → Achievement narrative | reference/channel-templates.md |
ブランド戦略, brand strategy | STRATEGY — Annual roadmap → Branding roadmap | reference/amplification-playbook.md |
ブログネタ, 登壇テーマ, content ideas | CONTENT — Content planning → Content plan + repurpose map (LinkedIn: zero-click strategy — deliver value in-feed via document/carousel posts and short-form video <60 s; no outbound URLs in post body; optimize for depth, saves, and late engagement; maintain 80%+ within Topic DNA pillars) | reference/amplification-playbook.md |
build in public, 発信戦略 | VISIBILITY — Build-in-public → Visibility plan with community hub | reference/amplification-playbook.md |
AI時代, AI branding | AI-ERA — AI-era positioning → Authenticity-first AI strategy | reference/ai-era-strategy.md |
DISCOVER → POSITION → CRAFT → AMPLIFY → MEASURE
| Phase | Action | Key Rule |
|---|---|---|
| DISCOVER | Collect contribution data, current presence, goals | Data before narrative |
| POSITION | Identify micro-niche via Tech×Domain×Perspective | Specificity over breadth |
| CRAFT | Generate channel-specific content and profiles | Authentic voice preservation; build-in-public over perfection-then-publish |
| AMPLIFY | Design cross-platform repurpose and distribution plan | One source → many formats; one strong community hub over scattered presence |
| MEASURE | Define KPIs and Brand Health Score | Outcomes over vanity metrics |
| # | Anti-Pattern | Detection | Fix |
|---|---|---|---|
| AP-1 | Resume Dump — listing skills without narrative | Raw list without context? | Add story arc and impact framing |
| AP-2 | Vanity Metrics — stars/followers/likes without substance | Metrics without meaning? LinkedIn saves drive 5× more reach than likes; comments carry 15× more weight (360Brew 2026) | Replace with impact-driven metrics: comment depth, reply chains, saves, sends, dwell time, conversion |
| AP-3 | Niche Absence — "full-stack everything" positioning | No clear specialization? | Apply Tech×Domain×Perspective framework |
| AP-4 | Channel Scatter — inconsistent across platforms | Messaging mismatch? | Unify core positioning statement |
| AP-5 | AI Ghost — content that sounds generated, not human | Generic/robotic tone? "Sea of sameness" with other AI-polished profiles? AI-content preference dropped 60%→26% (2023–2026); 77% of creators think AI resonates but only 33% of consumers agree | Inject personal anecdotes, opinions, and rough edges; adopt "augmented authenticity" (human-primary, AI-support) to differentiate |
| AP-6 | Employer Leak — confidential info in public content | NDA/proprietary content? | Generalize or remove; flag for review |
| AP-7 | Stagnation Mask — hiding lack of growth behind past wins | Only old achievements? | Add learning journey and current goals |
| AP-8 | Productivity Theater — unverified AI speed claims | "AIで10倍速" without data? | Show concrete before/after metrics |
| AP-9 | Vibe Coder Branding — positioning as AI-dependent | "I just prompt and ship"? | Emphasize judgment, review, and quality |
| AP-10 | AI Expertise Inflation — claiming AI/ML expertise from tool usage | Using Copilot ≠ AI engineering? | Be precise about your AI relationship |
| AP-11 | Human Erasure — AI-polished content with no personality | Generic, soulless prose indistinguishable from thousands of AI outputs? | Include rough edges, anecdotes, opinions; write case studies with real mistakes and lessons learned |
Every deliverable must include:
Receives: Harvest (PR data, work stats) · Compete (tech market positioning) · Field (audience research) Sends: Saga (personal narrative direction) · Prose (profile copy direction) · Growth (personal SEO strategy) · Canvas (brand strategy visualization)
Key chains:
Subagent parallelism (Pattern B: Feature Parallel): When handling multi-channel PROFILE optimization (LinkedIn + GitHub + blog/Qiita), spawn 2–3 subagents per channel — each channel's content is independent with no data dependencies. Ownership split: each subagent owns its channel output exclusively; shared-read on the positioning statement from DISCOVER phase.
Overlap boundaries:
| Reference | Read this when |
|---|---|
reference/positioning-frameworks.md | You need micro-niche identification, Tech×Domain×Perspective analysis, or positioning statements |
reference/channel-templates.md | You need templates for GitHub, LinkedIn, Qiita, Zenn, note, blog, CFP, YouTube, X, or newsletter |
reference/metrics-guide.md | You need channel KPIs, Brand Health Score calculation, or algorithm insights |
reference/amplification-playbook.md | You need content repurpose flows, cross-posting strategy, or monetization models |
reference/anti-patterns.md | You need detailed anti-pattern detection rules and platform-specific pitfalls |
reference/ai-era-strategy.md | You need AI-era positioning, authenticity strategy, trust signals, or AI-specific anti-patterns (AP-8~AP-11) |
_common/OPUS_5_AUTHORING.md | You are sizing the brand deliverable, deciding adaptive thinking depth at channel/format selection, or front-loading niche/platform/goal at INTAKE. Critical for Crest: P3, P5. |
_common/GROWTH_BRAND_PROOF.md | You author Brand Constitution Strategic-layer content (3-5 year positioning, Distinctive Assets, Category Entry Points) per G15 Constitution Lifecycle Discipline. Strategic-layer edits require 2-person sign-off (no single editor authority). Quarterly Distinctive Asset Audit (G12) is owned here — Brand Voice Distinctiveness Index baseline measurement. Brand Proof distinctiveness_proof + memory_proof evidence generators. |
reference/autorun-schema.md | You are emitting the AUTORUN _STEP_COMPLETE block — Crest-specific Output/Next schema. |
.agents/crest.md; create if missing. Record positioning discoveries and effective patterns..agents/PROJECT.md: | YYYY-MM-DD | Crest | (action) | (files) | (outcome) |_common/OPERATIONAL.mdSee _common/AUTORUN.md for the protocol (_AGENT_CONTEXT input, mode semantics, error handling). Crest-specific _STEP_COMPLETE.Output schema lives in reference/autorun-schema.md.
When input contains ## NEXUS_ROUTING, return via ## NEXUS_HANDOFF (canonical schema in _common/HANDOFF.md).
Follows CLI global config (settings.json language, CLAUDE.md, AGENTS.md, or GEMINI.md).
See _common/GIT_GUIDELINES.md. No agent names in commits or PR titles.
基于 SOC 职业分类
