Token导航 LogoToken导航TokenDH.com
开发敏感数据github未标认证来源可访问许可证需确认审计异常

intelligems-profit-impact智能利润影响

Agent Skill

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

总安装

245

周安装

10

GitHub Stars

2

下载量

78
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:intelligems-profit-impact(智能利润影响)
来源仓库:https://github.com/victorpay1/intelligems-analytics
仓库路径:skills/intelligems-profit-impact
安装命令:
npx skills add https://github.com/victorpay1/intelligems-analytics --skill intelligems-profit-impact
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/victorpay1/intelligems-analytics --skill intelligems-profit-impact

简介

用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。

  • 支持从来源仓库获取上下文,结合安装命令和原始 README 核验具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • 适用于需要自动化处理代码协作流程的场景,提升开发效率。
  • 可结合项目实际框架和协作规范使用,避免误操作影响生产环境。

SKILL.md

/intelligems-profit-impact

The CFO tool. Turns "+12% RPV" into "$47K/year" — the language that gets tests shipped.

Takes any Intelligems A/B test and projects the financial impact: conservative, expected, and optimistic annual revenue, break-even analysis, opportunity cost of delays, and a stakeholder-ready summary.


Step 0: Workspace Check

Check if the workspace exists:

ls ~/intelligems-analytics/venv/bin/activate 2>/dev/null && echo "READY" || echo "NEEDS_SETUP"

If NEEDS_SETUP: Copy and run the setup script from intelligems-core/references/:

bash ../intelligems-core/references/setup_workspace.sh

Then copy the core libraries:

cp ../intelligems-core/references/ig_client.py ~/intelligems-analytics/
cp ../intelligems-core/references/ig_metrics.py ~/intelligems-analytics/
cp ../intelligems-core/references/ig_helpers.py ~/intelligems-analytics/
cp ../intelligems-core/references/ig_config.py ~/intelligems-analytics/

Step 1: Get API Key

Check if the API key is already configured:

grep -v "your_api_key_here" ~/intelligems-analytics/.env 2>/dev/null | grep "INTELLIGEMS_API_KEY=" | head -1

If no valid key found, ask the user:

"What's your Intelligems API key? You can get one by contacting support@intelligems.io"

Then save it:

echo "INTELLIGEMS_API_KEY=<user's key>" > ~/intelligems-analytics/.env

Never hardcode or assume an API key.


Step 2: Copy Impact Script

Copy the profit impact script to the workspace:

cp references/impact.py ~/intelligems-analytics/impact.py

Also ensure the core libraries are up to date:

cp ../intelligems-core/references/ig_client.py ~/intelligems-analytics/
cp ../intelligems-core/references/ig_metrics.py ~/intelligems-analytics/
cp ../intelligems-core/references/ig_helpers.py ~/intelligems-analytics/
cp ../intelligems-core/references/ig_config.py ~/intelligems-analytics/

Step 3: Select Test

Run the script. If the user provided a test ID, pass it as an argument:

source ~/intelligems-analytics/venv/bin/activate && cd ~/intelligems-analytics && python3 impact.py

Or with a specific test ID:

source ~/intelligems-analytics/venv/bin/activate && cd ~/intelligems-analytics && python3 impact.py <test_id>

If no test ID is provided, the script lists all active experiments and prompts for selection.


Step 4: Run

The script outputs a full profit impact report to stdout. Let it run to completion.

If the script errors:

  • "No active experiments" — The store has no running tests. Let the user know.
  • "0 orders" — The test is too new. Suggest waiting for more data.
  • API errors — Check the API key is valid.

Step 5: Present Results

Read the script output and present it as a financial impact report. Frame everything in business terms:

  1. Lead with dollars — The annual impact number comes first, front and center
  2. Show the range — Conservative / Expected / Optimistic so stakeholders see the floor and ceiling
  3. Break-even framing — "You can afford to lose X% of conversions and still come out ahead"
  4. Urgency — "Every day you wait costs $X" drives action
  5. Business-case summary — 2-3 sentences ready to paste into a Slack message or email to leadership

Tone: Confident but not overselling. Use the conservative number when making the strongest claims. Lead with the expected number for impact, but always caveat with the range.

If the lift is negative: Still present the numbers honestly. Frame as "this variant would cost you $X/year" — knowing this is valuable too.

If confidence is low: Flag it prominently. "These projections carry higher uncertainty — the test needs more data before acting."


Step 6: Set Up Slack Automation (Optional)

If the user wants profit impact reports delivered to Slack, set up a Slack integration:

1. Get a Slack webhook URL

Ask the user:

"To send profit impact reports to Slack, you need an Incoming Webhook URL. Go to https://api.slack.com/apps → Create New App → Incoming Webhooks → Add New Webhook. Which channel should reports go to?"

2. Copy the Slack module

cp ../intelligems-core/references/ig_slack.py ~/intelligems-analytics/ig_slack.py

3. Test it

Run the impact report with the --slack flag:

cd ~/intelligems-analytics && source venv/bin/activate && python3 impact.py <test_id> --slack "<webhook_url>"

Verify the message appears in Slack with dollar projections, ranges, and business case summary.

4. Schedule it (optional)

Copy and run the automation setup script:

cp ../intelligems-core/references/setup_automation.sh ~/intelligems-analytics/
bash ~/intelligems-analytics/setup_automation.sh impact.py "<webhook_url>" 9 0

This creates a macOS LaunchAgent that runs the profit impact daily at 9:00 AM and posts to Slack.


Notes

  • Slack output: When using --slack, results are formatted as Slack Block Kit messages with annual impact, monthly breakdown, opportunity cost, and business case summary.
  • Terminal output: Without --slack, the report prints to the terminal as before.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

38.67%
按下载量换算30

Claude

30.18%
按下载量换算24

Cursor

18.36%
按下载量换算14

Gemini CLI

9.66%
按下载量换算8

安全审计

Gen Agent Trust Hub

未通过

Socket

通过

Snyk

未通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills