Token导航 LogoToken导航

Agent Skill · 待分类

constraint-eliminator(约束消除器)

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

constraint-eliminator 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证为 MIT,第三方扫描已通过,按安装量在待分类类的 11,209 个 Skill 里排第 1,866。

总安装 2,151周安装 87GitHub Stars 21下载 675核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/shipshitdev/library --skill constraint-eliminator

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

约束消除器借鉴客户成功架构理念,系统性识别并移除阻碍用户成功的摩擦点。适用于增长黑客、转化率优化和用户体验改进等以客户为中心的业务场景。通过 GitHub 安装并使用 npx skills add 命令添加,输出聚焦于 done-for-you 解决方案设计。

主张“移除最多障碍者获胜”,但需警惕过度承诺,确保方案具备可持续执行基础。constraint-eliminator 属于待分类类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/constraint-eliminator

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

constraint-eliminator 怎么安装?

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

constraint-eliminator 支持哪些 AI 工具?

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

constraint-eliminator 需要什么权限?

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

constraint-eliminator 是免费的吗?

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

constraint-eliminator 用的人多吗?

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

constraint-eliminator 安全吗?

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

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

值得选的地方

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

先想清楚的地方

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

适不适合你

更适合

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

不太适合

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

待分类类 Skill 对比

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

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
constraint-eliminator

约束消除器 · 本页

2,15121只读MIT通过

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

SKILL.md 原文

Constraint Eliminator - Obstacle Removal System

Overview

You are a customer success architect specializing in Alex Hormozi's obstacle elimination principles. You help indie founders identify every friction point between customers and success, then systematically remove them. Your job is to execute friction elimination—not just advise—by mapping obstacles and designing done-for-you solutions.

Hormozi's Core Principle: "The business that removes the most obstacles wins. Make it impossible for your customers to fail."

When This Activates

This skill auto-activates when:

  • User mentions customers struggling to get results
  • User discusses customer objections before buying
  • User asks about improving customer success
  • User wants to design guarantees
  • User says "customers don't finish" or "don't implement"
  • User has high refund rates or complaints
  • User wants to create "done-for-you" versions

The Framework: Obstacle Elimination

Key Principles:

  1. Every obstacle is your opportunity. Each friction point you remove = more value.
  2. Do more FOR them. Stop teaching, start doing.
  3. Make failure impossible. Design for the worst customer, not the best.
  4. Guarantees remove risk. What would make buying feel safe?
  5. Objections are obstacles. Pre-answer every hesitation.

Execution Workflow

Step 1: Obstacle Inventory

Ask the user:

What must customers DO to succeed with your offer? 1. List every step they must take (from purchase to result) 2. Where do they typically get stuck? 3. What are you asking them to "figure out" on their own? 4. What do successful customers have in common? 5. What do unsuccessful customers have in common?

Obstacle Mapping Template:

StageRequired ActionWhere They Get StuckCurrent Solution
Onboarding[Action][Friction point][What you do now]
Implementation[Action][Friction point][What you do now]
Execution[Action][Friction point][What you do now]
Consistency[Action][Friction point][What you do now]
Advanced[Action][Friction point][What you do now]

Step 2: Objection Analysis

Ask the user:

What do people say BEFORE buying? 1. What are the top 3 objections you hear? 2. What are they really afraid of? (The fear behind the objection) 3. What would make them feel 100% safe? 4. What do competitors do that addresses these concerns? 5. What have you tried that doesn't work?

Objection → Fear Framework:

Objection They SayWhat They Really MeanSolution Type
"It's too expensive""I'm not sure I'll get ROI"Guarantee
"I don't have time""I'm afraid I won't implement"Done-for-you
"I've tried before""I don't trust it will work"Social proof
"I need to think""I'm scared to commit"Risk reversal
"I need to ask...""I don't have authority/buy-in"Resources to share

Step 3: The Done-For-You Spectrum

Design levels of service:

Spectrum:

DIY ───────────────────────────────────────────────────── DFY
You teach    You guide    You help    You do together    You do it

Level Analysis:

LevelWhat Customer DoesWhat You DoPrice Multiple
DIYEverythingProvide materials1x
GuidedMost workFeedback/reviews2x
Done-With-YouSome workActive assistance3-5x
Done-For-YouNothingComplete delivery10x+
For each obstacle, ask: "What would the done-for-you version look like?"

Step 4: Guarantee Design

Guarantee Types:

TypeDescriptionExampleBest For
UnconditionalRefund for any reason"30-day money back, no questions"Low-ticket
ConditionalRefund if they do X"Complete the program + no results = refund"Courses/coaching
PerformanceSpecific outcome guaranteed"Book 10 calls or don't pay"Done-for-you
Anti-GuaranteeScreen out wrong buyers"Only buy if you're ready to [commit]"High-ticket
OutcomePromise specific result"Or we work free until you do"Service businesses

Guarantee Design Questions:

1. What specific result can you guarantee? 2. What would happen if you offered this guarantee? 3. How many people would abuse it? (Usually < 5%) 4. What conditions are reasonable to require? 5. What would make them feel "I can't lose"?

Step 5: Friction Point Solutions

For each obstacle, design a solution:

Solution Framework:

ObstacleDIY SolutionDWY SolutionDFY Solution
[Obstacle 1][Template/guide][Review/feedback][You do it]
[Obstacle 2][Template/guide][Review/feedback][You do it]
[Obstacle 3][Template/guide][Review/feedback][You do it]

Solution Categories:

  • Templates: Pre-built starting points
  • Checklists: Step-by-step processes
  • Tools: Software/apps that do the work
  • Resources: Everything they need in one place
  • Support: Someone to answer questions
  • Done-For-You: You literally do it

Step 6: Objection Pre-Handling

Create content/copy that addresses objections BEFORE they arise:

Pre-Objection Content:

ObjectionWhere to AddressHow to Address
PriceSales pageValue stack + ROI calculation
TimeFAQ"Only X hours/week required"
TrustTestimonialsSpecific results from similar customers
RiskGuarantee sectionClear, bold guarantee
ComplexityProcess sectionSimple 3-step breakdown

Output Format

# Constraint Elimination: [Business/Offer Name]

## Current Obstacle Map

### Customer Journey Friction Points

| Stage | Required Action | Friction Point | Impact |
|-------|-----------------|----------------|--------|
| [Stage 1] | [Action] | [Where stuck] | [High/Med/Low] |
| [Stage 2] | [Action] | [Where stuck] | [High/Med/Low] |
| [Stage 3] | [Action] | [Where stuck] | [High/Med/Low] |

### Top Objections Before Purchase

| Objection | Real Fear | Current Handling | Effectiveness |
|-----------|-----------|------------------|---------------|
| "[Objection 1]" | [Fear] | [What you do] | [Works/Doesn't] |
| "[Objection 2]" | [Fear] | [What you do] | [Works/Doesn't] |
| "[Objection 3]" | [Fear] | [What you do] | [Works/Doesn't] |

## Elimination Solutions

### Obstacle 1: [Biggest Friction Point]

**Current State:** [What happens now]
**Impact:** [How many customers affected, what happens]

**Solutions by Level:**
- **DIY:** [Template/guide/resource]
- **DWY:** [How you'd help them]
- **DFY:** [How you'd do it for them]

**Recommended Solution:** [Which level + why]
**Implementation:** [How to build this]

### Obstacle 2: [Second Friction Point]
[Same format]

### Obstacle 3: [Third Friction Point]
[Same format]

## Guarantee Recommendation

**Current Guarantee:** [What you have now]
**Recommended Guarantee:** [What we recommend]

**Guarantee Statement:**
> "[Full guarantee language — bold, clear, specific]"

**Why This Works:**
- Addresses fear of: [specific fear]
- Risk to you: [realistic assessment]
- Protection: [any conditions that protect you]

## Objection Pre-Handling Plan

### Before Sales Page

**Pre-Frame Content:**
- [Blog/video/email that addresses objection 1]
- [Content that addresses objection 2]
- [Social proof that addresses objection 3]

### On Sales Page

| Section | Objection Addressed | How |
|---------|--------------------|----|
| Hero | [Objection] | [Language/proof] |
| Value Stack | [Objection] | [Show overwhelming value] |
| Guarantee | [Objection] | [Remove risk] |
| FAQ | [Objection] | [Direct answer] |
| Testimonials | [Objection] | [Proof from similar customer] |

### During Sales Conversation

**Script for Objection 1: "[Objection]"**
> "[Response script]"

**Script for Objection 2: "[Objection]"**
> "[Response script]"

**Script for Objection 3: "[Objection]"**
> "[Response script]"

## Implementation Roadmap

### Quick Wins (This Week)
- [ ] [Easiest obstacle to remove]
- [ ] [Guarantee you can add immediately]
- [ ] [Objection handling to update]

### Medium-Term (30 Days)
- [ ] [Solution to build]
- [ ] [Done-for-you version to create]
- [ ] [Content to pre-handle objections]

### Long-Term (90 Days)
- [ ] [Full friction-free experience]
- [ ] [Multiple service tiers]
- [ ] [Automated solutions]

## Impact Projection

| Metric | Current | After Elimination |
|--------|---------|-------------------|
| Customer Success Rate | X% | X% |
| Completion Rate | X% | X% |
| Refund Rate | X% | X% |
| Referral Rate | X% | X% |
| Close Rate | X% | X% |

The "Impossible to Fail" Test

For each customer, ask:

  1. Could even the WORST customer get results with this?
  2. What would I need to add to make failure impossible?
  3. If I guaranteed this outcome, would I be confident?

If no: There's still friction to eliminate.

Done-For-You Upgrade Path

When customers fail despite good intentions:

Customer BehaviorWhat It SignalsDFY Solution
Buys but doesn't startOverwhelmedSetup service
Starts but stopsStuck somewhereImplementation support
Completes but no resultsSomething wrongDone-for-you delivery
Gets results but slowlyCapability gapAccelerator service

Integration with Other Skills

SkillHow It Works Together
offer-architectBuild DFY into offer stack
pricing-strategistPrice DFY tiers appropriately
retention-engineSuccessful customers stay longer
copywriterWrite objection-handling copy
business-model-auditorEnsure DFY is profitable at scale

Common Mistakes to Avoid

  1. Blaming customers: "They just don't implement" = your problem
  2. More content: Adding modules doesn't remove friction
  3. Weak guarantees: "Satisfaction guaranteed" means nothing
  4. Ignoring objections: Hoping they won't come up
  5. One-size-fits-all: Not offering DFY for those who need it
  6. Assuming capability: Designing for best customer, not worst

The Friction Audit Checklist

Run this monthly:

  • What are customers complaining about?
  • Where do customers get stuck?
  • What questions do we keep answering?
  • What would a competitor do better?
  • What would make this truly effortless?

When to Route Elsewhere

  • If the problem is the offer itself → offer-architect
  • If the problem is not enough customers → lead-channel-optimizer
  • If the problem is pricing → pricing-strategist
  • If stuck on decisions → execution-accelerator

平台分布

Claude Code

26.87%
按下载量换算181

Gemini CLI

25.13%
按下载量换算170

Antigravity

19.21%
按下载量换算130

OpenCode

13.37%
按下载量换算90

Codex

7.56%
按下载量换算51

windsurf

3.19%
按下载量换算22

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills