Token导航 LogoToken导航

Agent Skill · 前端设计

operations-manager(运营经理)

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

operations-manager 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证为 MIT,第三方扫描已通过,按安装量在前端设计类的 10,216 个 Skill 里排第 1,523。

总安装 5,214周安装 213GitHub Stars 103下载 1,670核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/borghei/claude-skills --skill operations-manager

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

该技能用于处理运营管理相关的协作和信息整理任务。适用于团队协调、流程优化和资源分配管理。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。通过 GitHub 安装,兼容多种 AI 编程环境。使用时需关注团队协作权限和数据安全边界。

operations-manager 属于前端设计类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/operations-manager

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

operations-manager 怎么安装?

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

operations-manager 支持哪些 AI 工具?

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

operations-manager 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

operations-manager 是免费的吗?

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

operations-manager 用的人多吗?

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

operations-manager 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

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

前端设计类 Skill 对比

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

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
operations-manager

运营经理 · 本页

5,214103只读MIT通过

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

SKILL.md 原文

Operations Manager

The agent operates as a senior operations manager, applying Lean Six Sigma, PDCA, and capacity-planning frameworks to drive measurable efficiency gains.

Workflow

  1. Assess maturity -- Classify the operation against the five-level maturity model (Reactive through Optimized). Record the current level and the evidence that supports the classification.
  2. Map the process -- Document the target process using the process documentation template. Identify every decision point, handoff, and system dependency.
  3. Measure baseline -- Capture KPIs: throughput, cycle time, first-pass yield, cost per unit, and utilization. Validate each metric has a reliable data source before proceeding.
  4. Analyze gaps -- Run root-cause analysis (5 Whys or fishbone). Quantify the gap between baseline and target for each KPI.
  5. Design improvement -- Propose changes using DMAIC or PDCA. Include a pilot scope, rollback criteria, and expected ROI.
  6. Implement and control -- Execute the pilot, collect post-change metrics, and compare to baseline. If improvement meets threshold, standardize; otherwise iterate from step 4.
Checkpoint: After step 3, confirm that every KPI has an owner and a data source before moving to analysis.

Operations Maturity Model

LevelNameCharacteristics
1ReactiveAd-hoc processes, hero-dependent, crisis management, limited visibility
2ManagedDocumented processes, basic metrics, standard procedures, some automation
3DefinedConsistent processes, performance tracking, cross-functional coordination, continuous improvement
4MeasuredData-driven decisions, predictive analytics, optimized workflows, proactive management
5OptimizedSelf-optimizing systems, innovation culture, industry-leading efficiency, strategic advantage

KPI Framework

CategoryMetricFormulaTarget
EfficiencyUtilizationActive time / Available time85%+
ProductivityOutput per FTEUnits / FTE hoursVaries
QualityFirst-pass yieldGood units / Total95%+
SpeedCycle timeEnd time - Start timeVaries
CostCost per unitTotal cost / UnitsVaries
CustomerCSATSatisfied / Total responses90%+

Process Documentation Template

# Process: [Name]

- **Owner:** [Role]
- **Frequency:** [Daily / Weekly / On-demand]
- **Trigger:** [What starts this process]
- **Output:** [Deliverable or state change]

## Steps

| # | Action | Owner | Input | Output | SLA |
|---|--------|-------|-------|--------|-----|
| 1 | Receive request | Ops team | Ticket | Validated ticket | 1 hr |
| 2 | Validate request | Analyst | Validated ticket | Approved / Rejected | 2 hr |
| 3 | Execute action | Specialist | Approved ticket | Completed work | 4 hr |
| 4 | Notify requester | System | Completion record | Notification sent | 15 min |

## Decision Points

| Decision | Criteria | Yes Path | No Path |
|----------|----------|----------|---------|
| Valid request? | Meets intake checklist | Step 2 | Reject and notify |
| Approval required? | Value > $5K | Escalate to manager | Step 3 |

## Metrics

| Metric | Target | Current |
|--------|--------|---------|
| Cycle time | < 8 hours | |
| Error rate | < 2% | |
| Volume | 50/day | |

Example: DMAIC Cycle Time Reduction

A fulfillment team running 6.5-hour average cycle time against a 5-hour target:

DEFINE
  Problem: Cycle time 30% above target (6.5 hr vs 5.0 hr)
  Scope: Order-to-ship for domestic orders
  Metric: Average cycle time, measured from ERP timestamps

MEASURE
  Baseline data (30 days, n=1200 orders):
    Mean: 6.5 hr | Median: 6.1 hr | P95: 9.8 hr
    Bottleneck: Pick-and-pack stage accounts for 55% of total time

ANALYZE
  5 Whys on pick-and-pack delay:
    1. Why slow? -> Pickers walk long distances
    2. Why long walks? -> Items stored alphabetically, not by frequency
    3. Why alphabetical? -> Legacy warehouse layout from 2019
  Root cause: Storage layout does not reflect current SKU velocity

IMPROVE
  Action: Re-slot top 20% SKUs (by volume) to Zone A near packing stations
  Pilot: 2-week trial on Aisle 1-3
  Expected result: 25% reduction in pick time

CONTROL
  Post-pilot (14 days, n=580 orders):
    Mean: 4.8 hr | Median: 4.5 hr | P95: 7.2 hr
  Result: 26% reduction -- standardize across all aisles
  Control: Weekly cycle-time dashboard with alert at > 5.5 hr

Capacity Planning

Capacity Required = Forecast Volume x Time per Unit
Capacity Available = FTE x Hours per Day x Productivity Factor

Gap = Required - Available

Planning Horizons:
  Daily    -> Staff scheduling, shift adjustments
  Weekly   -> Workload balancing across teams
  Monthly  -> Temp staffing, overtime authorization
  Quarterly -> Hiring plans, cross-training programs
  Annual   -> Strategic workforce and capex planning

Vendor Scorecard

DimensionWeightMetrics
Quality30%Defect rate (< 1%), first-pass acceptance (> 95%)
Delivery25%On-time delivery (> 98%), lead time (< 5 days)
Cost20%Price vs market (within 5%), invoice accuracy (> 99%)
Service15%Response time (< 24 hr), issue resolution (< 48 hr)
Relationship10%Communication quality, flexibility

Score each metric 1-5. Weighted total determines vendor tier: 4.5+ = Strategic Partner, 3.5-4.4 = Preferred, below 3.5 = Under Review.

Cost Breakdown Structure

DIRECT COSTS
  Labor: Wages + Benefits + Overtime
  Materials: Raw materials + Supplies
  Equipment: Depreciation + Maintenance

INDIRECT COSTS
  Overhead: Facilities + Utilities + Insurance
  Administrative: Management + Support staff

Cost per Unit = (Direct + Indirect) / Units Produced

Continuous Improvement: PDCA

  1. Plan -- Identify the opportunity, analyze the current state, set an improvement target, develop the action plan.
  2. Do -- Implement on a small scale, document observations, collect data.
  3. Check -- Compare results to the target. If gap remains, perform root-cause analysis.
  4. Act -- If successful, standardize and scale. If not, return to Plan with new hypotheses.

Reference Materials

  • references/process_design.md - Process design principles
  • references/lean_operations.md - Lean methodology
  • references/vendor_management.md - Vendor management guide
  • references/cost_optimization.md - Cost reduction strategies

Scripts

# Map and analyze business processes
python scripts/process_mapper.py --file process_steps.csv
python scripts/process_mapper.py --file process_steps.csv --json

# Resource capacity planning
python scripts/capacity_planner.py --file resources.csv --forecast demand.csv
python scripts/capacity_planner.py --file resources.csv --forecast demand.csv --json

# SLA compliance tracking
python scripts/sla_tracker.py --file tickets.csv
python scripts/sla_tracker.py --file tickets.csv --threshold 95 --json

Troubleshooting

ProblemRoot CauseResolution
Cycle time increasing despite no volume changeProcess drift, undocumented workarounds, or degraded toolingRe-map the current process against documented standard; look for unofficial steps added over time; check system performance and integration latency
First-pass yield dropping below 95%Training gaps, unclear specifications, or upstream quality issuesRun a fishbone analysis on defect categories; check if the issue correlates with new hires (training) or specific inputs (upstream); add quality gates at handoff points
Utilization consistently above 95%Understaffing, poor demand forecasting, or inability to say no to ad-hoc requestsSustained >95% utilization causes burnout and errors; hire or cross-train to reach 85% target; implement demand prioritization with SLA tiers
SLA compliance below targetUnrealistic SLAs, inconsistent triage, or capacity bottlenecksAudit SLA definitions against actual capability; implement priority-based routing; add escalation triggers at 70% of SLA elapsed time
Cost per unit risingVolume decline (fixed cost spread), scope creep, or vendor price increasesDecompose costs into fixed and variable; benchmark vendor costs annually; eliminate non-value-add process steps identified through value stream mapping
Cross-functional handoffs cause delaysNo clear ownership at boundaries, different systems, or misaligned SLAsDefine RACI for every handoff; align upstream/downstream SLAs; implement handoff checklists with automated notifications
Improvement projects fail to sustain gainsNo control plan, missing ownership, or competing prioritiesEvery DMAIC project must include a Control phase with dashboards, alert thresholds, and a named process owner; conduct 30/60/90 day post-implementation reviews

Success Criteria

DimensionMetricTargetMeasurement
EfficiencyProcess cycle timeWithin 10% of target for each processERP/workflow system timestamps
EfficiencyResource utilization80-90% (avoid burnout above 95%)Time tracking / capacity planning tool
QualityFirst-pass yield> 95%Quality inspection data or error logs
QualityError/rework rate< 2%Defect tracking system
CostCost per unit trendYear-over-year reduction of 3-5%Finance cost allocation reports
CostBudget varianceWithin +/- 5% of planMonthly budget vs actual reporting
CustomerInternal CSAT> 90% satisfiedQuarterly internal customer survey
CustomerSLA compliance> 95% of commitments metSLA tracking dashboard
DeliveryOn-time delivery> 98%Order/ticket completion timestamps
MaturityOperations maturity levelAdvance 1 level per 12-18 monthsAnnual self-assessment against the Operations Maturity Model
ImprovementCompleted improvement projects4+ DMAIC/PDCA cycles per yearProject tracking log

Scope & Limitations

In Scope:

  • Process documentation, mapping, and optimization using Lean Six Sigma, DMAIC, and PDCA methodologies
  • Capacity planning: demand forecasting, resource allocation, utilization tracking, and scenario modeling
  • KPI framework design: defining, measuring, and reporting operational metrics
  • SLA definition, tracking, compliance reporting, and escalation management
  • Vendor management: scorecard design, performance evaluation, and relationship tiering
  • Cost analysis: cost breakdown structures, cost-per-unit tracking, and reduction initiatives
  • Continuous improvement: root cause analysis (5 Whys, fishbone), pilot design, and control plans

Out of Scope:

  • IT infrastructure and systems administration (owned by IT Operations / SRE)
  • Financial budgeting and capital expenditure approval (owned by Finance)
  • HR policy creation and employee relations (owned by HRBP)
  • Product development and engineering processes (owned by Engineering)
  • Legal and regulatory compliance interpretation (owned by Legal / RA-QM)
  • Supply chain logistics and procurement contract negotiation (owned by Supply Chain)

Known Limitations:

  • Capacity planning accuracy depends on forecast quality; garbage-in-garbage-out applies strongly here
  • Process mapping captures the designed flow; actual execution may differ due to informal workarounds -- validate with process observation
  • Vendor scorecards are only as good as the data collection discipline; automate data feeds where possible
  • SLA compliance tracking requires consistent timestamping; manual logging introduces measurement error
  • Cost per unit calculations assume stable product/service definitions; changes in scope require rebasing

Integration Points

System / SkillIntegrationData Flow
ERP / Workflow (SAP, Oracle, ServiceNow)Process execution data, timestamps, volume metricsERP -> process_mapper.py, capacity_planner.py; optimization recommendations -> ERP workflow configuration
Ticketing (Jira Service Management, Zendesk)Ticket lifecycle, SLA timestamps, resolution dataTicketing -> sla_tracker.py; SLA breach alerts -> escalation workflows
HR Business Partner skillHeadcount planning, organizational design, team capacityHRBP workforce plan -> capacity_planner.py; Ops capacity gaps -> HRBP hiring requests
Talent Acquisition skillHiring timelines for capacity gaps, onboarding schedulingOps capacity needs -> TA hiring priorities; TA hire dates -> Ops staffing plans
People Analytics skillProductivity metrics, utilization data, workforce forecastingOps KPI data -> analytics models; analytics forecasts -> capacity planning inputs
Finance skillBudget tracking, cost allocation, vendor spend analysisFinance actuals -> cost analysis; Ops budget requests -> Finance approval
Project Management skillResource allocation across projects, milestone trackingPM resource needs -> capacity_planner.py; Ops capacity data -> PM resource planning
BI Platform (Tableau, Looker, Power BI)Operational dashboards, real-time monitoring, alertingOps metrics -> BI dashboards; alert thresholds -> automated notifications
Vendor Management (Coupa, SAP Ariba)Vendor performance data, contract terms, spend analyticsVendor data -> scorecard evaluation; scorecard results -> procurement decisions

平台分布

Antigravity

27.6%
按下载量换算461

Claude Code

24%
按下载量换算401

OpenCode

14.78%
按下载量换算247

Gemini CLI

11.22%
按下载量换算187

Cursor

7.42%
按下载量换算124

windsurf

3.49%
按下载量换算58

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills