Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add MetaInFLow/Enterprise-ai-scenario-map-skill --skill enterprise-ai-scenario-map-skillgit clone --depth 1 https://github.com/MetaInFLow/Enterprise-ai-scenario-map-skillWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/metainflow/enterprise-ai-scenario-map-skill/enterprise-ai-scenario-map-skill)<a href="https://agentmods.dev/skills/metainflow/enterprise-ai-scenario-map-skill/enterprise-ai-scenario-map-skill"><img src="https://agentmods.dev/badge/skills/metainflow/enterprise-ai-scenario-map-skill/enterprise-ai-scenario-map-skill/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/metainflow/enterprise-ai-scenario-map-skill/enterprise-ai-scenario-map-skill"><img src="https://agentmods.dev/badge/skills/metainflow/enterprise-ai-scenario-map-skill/enterprise-ai-scenario-map-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00066 | $0.04450 |
| Opus 5 | $0.00033 | $0.02225 |
| Sonnet 5 | $0.00013 | $0.00890 |
| Haiku 4.5 | $0.00007 | $0.00445 |
Grade A, and why
enterprise-ai-scenario-map scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
企业AI场景地图生成器
任务目标
- 本Skill用于:为企业生成AI应用场景地图报告,帮助决策者快速识别可应用的AI场景及优先级
- 核心价值:让企业老板快速知道公司哪些场景可以用AI,应该优先启动哪些
- 能力包含:
- 企业深度调研(公司信息、主营业务、产品、行业标签)
- 业务特性与流程分析
- 同行业AI最佳实践案例搜索
- AI应用场景地图生成(30+场景全量表,含优先级建议)
- 实施路径规划(分阶段落地计划)
- 触发条件:用户需要为某家企业制定AI落地规划,或想了解"我的公司如何用AI"
前置准备
- 依赖说明:
- 智能体需要具备 web-search(网络搜索)工具能力
- Python 3.8+(用于运行调研框架生成脚本)
- 无第三方 Python 包依赖
操作步骤
核心工作流程(严格按顺序执行)
重要:必须完成搜索后才能进入分析和报告生成阶段
阶段1:深度调研(数据收集)
必须先完成此阶段,才能进入分析阶段
步骤1.1:生成调研框架
运行脚本生成调研框架和搜索问题清单:
python scripts/deep_research_wrapper.py --company-name "<公司名称>" --country "<国家>"
脚本会输出:
- 企业调研框架(基础结构)
- 企业信息搜索问题清单(8个核心问题)
- 行业信息搜索问题清单(痛点 + 案例)
步骤1.2:企业信息深度调研
使用 web-search 工具,逐一搜索步骤1.1输出的「企业信息搜索问题清单」,收集以下信息:
- 公司基本信息(成立时间、规模、主营业务)
- 业务模式(B2B/B2C/平台型/混合型)
- 核心业务环节
- 关键业务流程
- 客户类型
- 业务特点
- 团队规模(如有公开信息)
步骤1.3:行业痛点与案例收集
使用 web-search 工具,按步骤1.1输出的「行业信息搜索问题清单」进行搜索(必须按顺序):
搜索A:行业共性痛点
搜索关键词:<行业> + 痛点 + 挑战 + 2024 2025
收集内容:
- 行业面临的普遍痛点
- 典型表现和影响
- 量化数据(如有)
搜索B:行业AI应用案例
搜索关键词:<行业> + AI应用 + 智能化 + 案例
搜索关键词:<具体业务> + AI + LLM + 实践
收集内容:
- 至少3个标杆企业案例
- 每个案例包含:企业背景、应用场景、技术方案、实施效果、关键成功因素
阶段1完成标志:所有搜索完成,信息已整理成结构化文档
阶段2:分析与诊断(仅在阶段1完成后开始)
步骤2.1:业务特性分析 参考 references/business-analysis-framework.md,分析:
- 业务特性概述(服务模式、专业要求、业务协同、知识依赖、客户特征)
- 内部流程特点(流程特点1-4及AI赋能方向)
步骤2.2:核心痛点诊断 基于阶段1收集的痛点信息,分析:
- 行业共性痛点(4个)
- 企业经营痛点(效率、质量、风险、成本、知识五个维度)
步骤2.3:对标启示总结 基于收集的行业案例,总结:
- 4个关键启示
- 每个启示的说明和建议行动
阶段3:场景地图生成(仅在阶段2完成后开始)
步骤3.1:业务流程拆解 根据企业主营业务,拆解核心业务流程,格式示例:
项目立项 → 预算编制&造价 → 招标代理&评标 → 合同管理&变更 → 工程结算&审计
步骤3.2:AI场景全量表生成(30+场景) 参考 references/typical-ai-scenarios.md,生成场景全量表,包含以下列: | 序号 | 业务环节 | AI场景名称 | 功能描述 | 实施前提 | 预期收益 | 优先级 |
场景生成要求:
- 场景总数必须达到30个以上
- 按业务环节分类(至少5个环节)
- 每个场景必须包含:功能描述、实施前提、预期收益、优先级(🟢/🟡/🔵)
优先级定义(参考 references/scenario-priority-framework.md):
- 🟢 快速启动(0-3个月):技术成熟、实施快、见效快
- 🟡 中期建设(3-12个月):需要一定基础建设,价值高
- 🔵 长期演进(1年以上):需要深度积累,战略价值高
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 381 lines · 66 tokens per session scan A af4bebedf71e
enterprise-ai-scenario-map is a skill published in the GitHub repository MetaInFLow/Enterprise-ai-scenario-map-skill (631 stars, last pushed 5mo ago), licensed MIT. It adds 66 tokens to every session and 4,450 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…