Token导航 LogoToken导航

Agent Skill · 研究检索

problem-solving(解决问题)

problem-solving 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

problem-solving 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 59,579。

总安装 384周安装 16GitHub Stars 471下载 128核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/aitytech/agentkits-marketing --skill problem-solving

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

problem-solving 用于查找、检索和筛选相关信息。适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词快速定位候选结果。通过 npx skills add 命令从指定仓库安装并使用。需确认权限范围和维护状态,注意是否触发联网或文件读写操作。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/problem-solving

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

problem-solving 怎么安装?

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

problem-solving 支持哪些 AI 工具?

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

problem-solving 需要什么权限?

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

problem-solving 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

problem-solving 用的人多吗?

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

problem-solving 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

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

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
problem-solving

解决问题 · 本页

384471只读未明确有提醒

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

SKILL.md 原文

Marketing Problem-Solving

Systematic techniques for solving complex marketing challenges, breaking through creative blocks, and optimizing campaigns.

Language & Quality Standards

CRITICAL: Respond in the same language the user is using. If Vietnamese, respond in Vietnamese. If Spanish, respond in Spanish.

Standards: Token efficiency, sacrifice grammar for concision, list unresolved questions at end.


When to Use This Skill

Apply problem-solving techniques when facing:

  • Campaign Complexity Spirals - Campaign keeps adding features/channels, becoming unwieldy
  • Creative Innovation Blocks - Stuck in conventional approaches, need breakthrough ideas
  • Recurring Campaign Patterns - Same issues appearing across multiple campaigns
  • Assumption Constraints - Limited by industry "truths" or conventional wisdom
  • Audience Scale Uncertainty - Unclear how strategy scales from niche to mass market
  • General Stuckness - Progress halted, unclear how to move forward

Core Techniques

1. Simplification Cascades

Problem: Campaign complexity spiraling out of control

When to use:

  • Campaign has too many channels, messages, or touchpoints
  • Team overwhelmed by execution complexity
  • Budget spread too thin across tactics
  • Message diluted across too many variations

How it works:

  1. List all campaign elements (channels, messages, segments, assets)
  2. Identify the 20% that drives 80% of results
  3. Ruthlessly cut the rest
  4. Reassess and repeat if still complex

Marketing example:

Problem: Product launch campaign across 8 channels, 15 assets, 4 segments
↓ Simplification Round 1
Focus: Top 3 channels (email, LinkedIn, blog), 6 core assets, 2 key segments
↓ Simplification Round 2
Core: Email + LinkedIn, 3 assets (landing page, case study, email sequence), 1 primary segment
Result: Focused execution, better results, manageable workload

See: ./references/simplification-cascades.md


2. Collision-Zone Thinking

Problem: Creative blocks, conventional approaches not working

When to use:

  • Campaign ideas feel generic or uninspired
  • Competitor campaigns all look similar
  • Need differentiation and breakthrough positioning
  • Stuck in industry best practices that don't work

How it works:

  1. Identify two unrelated domains/industries
  2. Force collision: "What if [industry A] met [industry B]?"
  3. Extract unexpected insights
  4. Apply to your marketing challenge

Marketing example:

Challenge: B2B SaaS email campaign feels boring
Collision: "What if enterprise software marketing met sneaker drops?"
Insights: Scarcity, hype, exclusive access, community building
Application: Limited beta access campaign, waitlist with perks, exclusive Slack community
Result: 3x higher engagement, viral social sharing

See: ./references/collision-zone-thinking.md


3. Meta-Pattern Recognition

Problem: Same issues recurring across campaigns

When to use:

  • Different campaigns failing in similar ways
  • Repeated performance issues across channels
  • Team making same mistakes
  • Need to identify root cause vs symptoms

How it works:

  1. Document 3+ instances of similar failures
  2. Look for deeper pattern beneath surface issues
  3. Address root cause, not symptoms
  4. Create system to prevent recurrence

Marketing example:

Surface problems:
- Email campaign: Low open rates
- Social campaign: Low engagement
- Content campaign: Low traffic

Meta-pattern discovered: Weak audience understanding
Root cause: No buyer persona research or validation
Solution: Comprehensive persona development process
Prevention: Mandatory persona validation before any campaign

See: ./references/meta-pattern-recognition.md


4. Inversion Exercise

Problem: Constrained by industry assumptions or "best practices"

When to use:

  • Conventional approaches failing
  • Industry "rules" limiting creativity
  • Need to challenge assumptions
  • Market leader doing opposite of conventional wisdom

How it works:

  1. State current assumption: "We must do X"
  2. Invert it: "What if we did the opposite of X?"
  3. Explore inverted scenario seriously
  4. Identify valid insights from inversion

Marketing example:

Assumption: "We must build email list before launching"
Inversion: "What if we launched with zero email list?"
Exploration: Focus on virality, referrals, paid acquisition, partnerships
Insight: Email list might be vanity metric; focus on product-led growth
Result: Skip content marketing, invest in product experience and referral program

See: ./references/inversion-exercise.md


5. Scale Game

Problem: Uncertain how strategy scales across audience sizes

When to use:

  • Unclear if niche strategy works at scale
  • Planning market expansion
  • Pivot from early adopters to mainstream
  • Budget allocation across segments uncertain

How it works:

  1. Test strategy at 10x smaller scale
  2. Test strategy at 10x larger scale
  3. Identify what breaks at each scale
  4. Design for actual scale, not current size

Marketing example:

Current: 100 customers via founder-led sales

10x smaller (10 customers):
- Works: Personal outreach, custom demos, high-touch
- Breaks: Can't justify any paid marketing

10x larger (1,000 customers):
- Works: Content marketing, paid ads, self-service onboarding
- Breaks: Founder-led sales, custom demos

10x larger again (10,000 customers):
- Works: Product-led growth, brand awareness, partnerships
- Breaks: Content marketing bandwidth, ad costs unsustainable

Insight: At 100→1,000, invest in content + paid ads + self-service
Don't optimize for 10 or 10,000; build for 1,000

See: ./references/scale-game.md


6. When Stuck Protocol

Problem: Progress completely halted, don't know next step

When to use:

  • Campaign stalled with no clear path forward
  • Team disagrees on approach
  • Overwhelmed by options or complexity
  • Decision paralysis

How it works:

  1. Zoom out: What's the actual goal? (Often forgot amid tactics)
  2. Constraint: What if you had 1 day and $100? (Forces prioritization)
  3. Naïve question: What would a beginner do? (Often surprisingly insightful)
  4. Ship smallest: What's the absolute minimum to test hypothesis?

Marketing example:

Stuck: Launching new product, paralyzed by marketing plan complexity

Zoom out: Goal = validate market demand + get 10 paying customers

Constraint: 1 day + $100 budget
- Can't build full funnel
- Can't create 50 assets
- Focus: Simple landing page + $100 LinkedIn ads

Naïve approach: "Just tell people about it"
- Direct outreach to 50 ideal customers
- Simple email explaining value

Ship smallest: Landing page + email to 50 prospects + $100 ads
Result: 3 sales in week 1, validated demand, iterate from there

See: ./references/when-stuck.md


Problem-Solving Workflow

Step 1: Identify Problem Type

  • Complexity spiral? → Simplification Cascades
  • Creative block? → Collision-Zone Thinking
  • Recurring pattern? → Meta-Pattern Recognition
  • Assumption constraint? → Inversion Exercise
  • Scale uncertainty? → Scale Game
  • Completely stuck? → When Stuck Protocol

Step 2: Apply Technique

  • Follow structured process for chosen technique
  • Document insights and findings
  • Validate assumptions with data/research

Step 3: Implement Solution

  • Create action plan from insights
  • Test solution at small scale first
  • Measure results and iterate

Step 4: Capture Learning

  • Document problem + solution for future reference
  • Share with team to build knowledge base
  • Update campaign playbooks with insights

Integration with Marketing Workflow

Use problem-solving techniques at these key moments:

Planning Phase:

  • Scale Game: Validate strategy for target audience size
  • Inversion Exercise: Challenge conventional approaches

Execution Phase:

  • Simplification Cascades: Cut scope when overwhelmed
  • When Stuck Protocol: Unblock campaign development

Optimization Phase:

  • Meta-Pattern Recognition: Identify recurring issues
  • Collision-Zone Thinking: Generate breakthrough ideas

Review Phase:

  • Document learnings for future campaigns
  • Update problem-solving playbook

Reference Materials

All techniques detailed in ./references/:

  • simplification-cascades.md - Reducing campaign complexity
  • collision-zone-thinking.md - Breaking creative blocks
  • meta-pattern-recognition.md - Finding root causes
  • inversion-exercise.md - Challenging assumptions
  • scale-game.md - Planning for audience scale
  • when-stuck.md - Unblocking progress
  • attribution.md - Framework origins and credits

Quick Reference

Complexity overwhelm? → Simplification Cascades (cut to 20% that matters) Creative stuck? → Collision-Zone Thinking (force unexpected combinations) Same problems repeating? → Meta-Pattern Recognition (find root cause) Best practices failing? → Inversion Exercise (try opposite approach) Scaling unclear? → Scale Game (test at 10x/0.1x scale) Completely blocked? → When Stuck Protocol (zoom out, constrain, ship smallest)


Remember: These techniques are tools, not rules. Mix and combine as needed. The goal is breakthrough thinking and unblocked execution, not perfect methodology.

平台分布

Codex

37.95%
按下载量换算49

Claude

31.91%
按下载量换算41

Cursor

17.65%
按下载量换算23

Gemini CLI

8.79%
按下载量换算11

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills