Token导航 LogoToken导航

Agent Skill · AI 工具

promotion-preparation(促销准备)

promotion-preparation 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

promotion-preparation 是AI 工具类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证为 MIT,第三方扫描已通过,按安装量在AI 工具类的 2,536 个 Skill 里排第 1,769。

总安装 480周安装 20GitHub Stars 61下载 160核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:promotion-preparation(促销准备)
来源仓库:https://github.com/melodic-software/claude-code-plugins
仓库路径:skills/promotion-preparation
安装命令:
npx skills add https://github.com/melodic-software/claude-code-plugins --skill promotion-preparation
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/melodic-software/claude-code-plugins --skill promotion-preparation

这个 Skill 是做什么的

AI 工具类 Skill 用来扩展助手本身的能力,例如接模型、接检索、接外部服务。

promotion-preparation 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理时使用。适用于上线前检查清单生成、发布门禁控制和回滚预案准备场景。

支持依赖项版本锁定和数据库迁移脚本验证。使用前需确认 CI/CD 流水线集成状态。建议设置灰度发布比例阶梯,降低全量风险。

来源仓库内路径:skills/promotion-preparation

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/melodic-software/claude-code-plugins --skill p…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

promotion-preparation 怎么安装?

在终端执行 npx skills add https://github.com/melodic-software/claude-code-plugins --skill promotion-p…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

promotion-preparation 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

promotion-preparation 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

promotion-preparation 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

promotion-preparation 用的人多吗?

公开数据是累计安装 480 次,近一周安装 20 次,下载 160 次,GitHub 61 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

promotion-preparation 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理AI 工具类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

AI 工具类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
executing-plans

执行计划 · Codex、Claude

1,515,336173,110只读MIT通过
verification-before-completion

完成前的验证 · Codex、Claude

1,319,472173,121权限未标注MIT通过
subagent-driven-development

子 Agent 驱动开发 · Codex、Claude

1,312,416173,138只读MIT通过
copy-editing

复制编辑 · Codex、Claude

1,209,57625,632只读MIT通过
paywall-upgrade-cro

付费专区升级 cro · Codex、Claude

1,030,17625,617只读MIT通过
promotion-preparation

促销准备 · 本页

48061需要联网MIT通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Promotion Preparation

This skill provides frameworks for building compelling promotion cases, maintaining brag documents, tracking accomplishments, and effectively advocating for your career advancement.

Keywords

promotion, brag document, promotion case, self-advocacy, wins, accomplishments, impact, career advancement, tracking wins, promotion document, manager alignment, performance review, evidence-based promotion

When to Use This Skill

  • Building a promotion case document
  • Starting or maintaining a brag document
  • Tracking and categorizing accomplishments
  • Preparing for performance reviews
  • Understanding what managers look for
  • Learning to advocate for yourself
  • Documenting impact and contributions

Core Principle: You Own Your Promotion

Critical insight: Promotions are not handed out - they are earned and advocated for.

Your manager:

  • Cannot remember all your accomplishments
  • Has limited time to build your case
  • Needs your help to advocate for you
  • Wants you to succeed but needs evidence

Your responsibility:

  • Track your own wins consistently
  • Build your promotion case proactively
  • Communicate impact clearly
  • Align with manager on expectations
  • Make it easy for your manager to promote you

The Promotion Case Document

A promotion case document is your comprehensive argument for advancement. It serves multiple purposes:

  • Provides evidence for promotion discussions
  • Helps your manager advocate for you
  • Forces you to articulate your impact
  • Identifies gaps you can address

Three-Section Structure

1. Accomplishments & Impact (What You've Done)

Document specific achievements with measurable outcomes:

  • Projects delivered and their business impact
  • Problems solved and value created
  • Technical contributions and innovations
  • Process improvements and efficiency gains
2. Growth & Learning (How You've Developed)

Show trajectory and development:

  • Skills acquired or deepened
  • Challenges overcome
  • Feedback incorporated
  • Areas of improvement demonstrated
3. Future Focus (What You'll Do Next)

Demonstrate readiness for next level:

  • Goals aligned to next-level expectations
  • Larger scope you're ready to take on
  • Development areas you're addressing
  • Vision for your expanded role

Brag Document Fundamentals

A brag document (also called "work log" or "wins journal") is your ongoing record of accomplishments.

Why Keep a Brag Document?

  • Memory is unreliable: You forget 80% of what you did by review time
  • Recency bias: Recent work overshadows earlier achievements
  • Cumulative impact: Small wins add up to significant patterns
  • Confidence building: Reviewing wins combats imposter syndrome
  • Interview prep: Ready-made STAR stories for future opportunities

Cadence

FrequencyActivity
WeeklyQuick bullet points of wins (5-10 min)
MonthlyReview and expand bullets, add context
QuarterlySynthesize themes, identify patterns
AnnuallyBuild promotion case from accumulated evidence

What to Capture

For each win, capture:

  • What: The specific accomplishment
  • How: Your approach and actions
  • Impact: Measurable outcomes (quantify when possible)
  • Skills: What this demonstrates
  • Category: Type of contribution (see Win Categorization)

Win Categorization

Not all wins are created equal. Categorize to show breadth:

Impact Types

TypeDescriptionExample
DeliveryShipped features, projects, products"Launched payment v2, processing $2M/day"
QualityImproved reliability, reduced bugs"Reduced error rate from 2% to 0.1%"
EfficiencyFaster, cheaper, better processes"Cut deploy time from 2 hours to 15 min"
InnovationNew approaches, creative solutions"Introduced caching strategy saving $50K/year"
LeadershipMentoring, leading, enabling others"Mentored 2 engineers to senior level"
CollaborationCross-team work, partnerships"Led joint initiative with 3 teams"

Scope Levels

ScopeDescriptionNext Level Signal
IndividualYour personal contributionExpected at current level
TeamImproved your team's outcomesMid → Senior
Multi-teamImpact across multiple teamsSenior → Staff
Org-wideShaped organizational outcomesStaff → Principal

Self-Advocacy Skills

Making Your Work Visible

Visibility is not self-promotion - it's professional communication:

  1. Status updates: Regular, concise updates on progress
  2. Demo your work: Present at team meetings, tech talks
  3. Document decisions: Write design docs, ADRs, post-mortems
  4. Share learnings: Blog posts, knowledge sharing sessions
  5. Volunteer for visibility: All-hands demos, cross-team presentations

Articulating Impact

Weak: "I worked on the new API"

Strong: "I designed and implemented the new payments API, which reduced integration time from 2 weeks to 2 days and enabled 3 new partner integrations in Q3"

Formula: Action + Specifics + Measurable Outcome

Working with Your Manager

  1. Align on expectations: What does next level look like specifically?
  2. Share your goals: Make your promotion aspirations known
  3. Regular check-ins: Use 1:1s to discuss progress
  4. Ask for feedback: What gaps exist? What would make the case stronger?
  5. Request opportunities: Ask for stretch assignments aligned to next level

Common Mistakes

In Tracking Wins

  • Waiting too long: Weekly tracking beats quarterly scrambles
  • Being too modest: Document everything, filter later
  • Only big wins: Small wins show consistency
  • Skipping context: Future-you won't remember details
  • No quantification: Numbers make impact concrete

In Building the Case

  • Too generic: "I'm a good team player" vs specific examples
  • Missing business impact: Technical achievements without business context
  • No growth narrative: List of tasks vs story of development
  • Ignoring gaps: Pretending weaknesses don't exist vs addressing them
  • Going alone: Not aligning with manager throughout

In Self-Advocacy

  • Assuming merit is enough: Great work must be visible
  • Waiting to be noticed: Proactive communication is expected
  • Over-advocating: Balance confidence with humility
  • Wrong audience: Tailor message to stakeholders
  • Timing: Don't wait until review time to start

Manager's Perspective

Understanding how managers view promotions helps you prepare effectively:

What managers need:

  • Clear evidence to present to their managers
  • Confidence that you'll succeed at next level
  • Reduced risk of "promoting too early"
  • Peer-level support for the promotion

What makes promotion easy:

  • Well-documented accomplishments with impact
  • Already operating at next level
  • No significant concerns or gaps
  • Clear narrative they can tell

What makes promotion hard:

  • Vague contributions hard to articulate
  • Gaps in critical competencies
  • Inconsistent performance
  • Lack of peer support or visibility

Building Your Promotion Timeline

6 Months Before Review

  • Start or refresh brag document
  • Align with manager on promotion goals
  • Identify gaps and create development plan
  • Seek stretch assignments

3 Months Before Review

  • Begin drafting promotion case
  • Review against next-level expectations
  • Gather supporting evidence (docs, metrics)
  • Get feedback on draft from manager

1 Month Before Review

  • Finalize promotion document
  • Ensure manager has everything needed
  • Prepare talking points
  • Document recent wins

At Review Time

  • Be prepared to discuss your case
  • Listen to feedback openly
  • If not promoted, understand gaps and plan
  • Continue tracking for next cycle

References

For detailed guidance, see:

  • references/promotion-case-structure.md - Complete promotion document template with examples
  • references/brag-document-guide.md - Weekly/monthly tracking templates and tips
  • references/win-categorization.md - Multi-dimensional win classification framework
  • references/manager-perspective.md - What managers look for, how to align

Related Skills

  • career-strategy - Level expectations, progression paths, and career planning
  • career-strategy - Internal vs external growth decisions
  • interview-skills - Using accomplishments in interviews

Related Commands

  • /soft-skills:promotion-preparation - Generate a structured promotion case document
  • /soft-skills:track-win - Document an accomplishment in brag document format

User-Facing Interface

When invoked directly by the user, this skill supports two workflows: building a promotion case and assessing career readiness.

Build Promotion Case Workflow

When invoked with role arguments (e.g., <current-role> <target-role> [achievements...]):

  1. Parse Arguments - Extract current role, target role, and any key achievements listed.
  2. Gather Context - If achievements are sparse, ask probing questions about projects delivered, business impact, leadership activities, and growth trajectory.
  3. Load Level Expectations - Reference career-strategy skill for target level competency expectations.
  4. Structure Promotion Case - Generate a three-section promotion document:

- Accomplishments & Impact - Specific achievements with quantified outcomes - Growth & Learning - Skills developed, challenges overcome, feedback incorporated - Future Focus - Goals aligned to next-level expectations, expanded scope readiness

  1. Identify Gaps - Highlight areas where the case could be strengthened with more evidence or development.
  2. Save Results - Offer to save the promotion case document.

Assess Readiness Workflow

When invoked with assessment intent (e.g., promotion, job-change, level <target>):

  1. Parse Arguments - Determine assessment type (promotion readiness, job change readiness, or level assessment).
  2. Gather Self-Assessment Data - Ask structured questions about current contributions, scope of impact, competency demonstration, and visibility.
  3. Evaluate Against Framework - Score readiness across competency categories (Technical, Design, Operations, Product, Leadership, Communication).
  4. Generate Readiness Report - Produce assessment with:

- Overall readiness score and recommendation - Strength areas with evidence - Gap areas with specific development actions - Suggested timeline and next steps

  1. Recommend Actions - Prioritized list of actions to close gaps before pursuing advancement.

Version History

  • v1.0.0 (2025-12-26): Initial release

Last Updated

Date: 2025-12-26 Model: claude-opus-4-5-20251101

平台分布

Antigravity

27.63%
按下载量换算44

windsurf

22.25%
按下载量换算36

Claude Code

17.43%
按下载量换算28

trae

11.49%
按下载量换算18

Codex

8.4%
按下载量换算13

OpenCode

3.24%
按下载量换算5

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills