菜单
Convert external GTM signals (LinkedIn posts, conference programme pages, industry pages) into engineering-first ACE artifacts, then derive wiki and GTM updates with explicit evidence boundaries.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/vamseeachanta/workspace-hub --skill gtm-signal-to-engineering-artifact-conversion命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | gtm-signal-to-engineering-artifact-conversion |
| description | Convert external GTM signals (LinkedIn posts, conference programme pages, industry pages) into engineering-first ACE artifacts, then derive wiki and GTM updates with explicit evidence boundaries. |
| version | 1.0.0 |
| category | workspace-hub-learned |
| tags | ["gtm","engineering","wiki","linkedin","conference-signals","parallel-agents"] |
| applies-to | ["hermes","Codex","codex"] |
| trigger | manual |
| auto_execute | false |
Use when the input is an external market/content signal (LinkedIn post, conference programme, industry page) and the user wants ACE GTM/wiki work updated without drifting into hype.
Treat public posts/programmes as:
Do NOT treat them as:
Always convert the signal into an engineering artifact first, then derive GTM/web copy later.
Use browser tools to capture:
Summarize in two buckets:
Read the current ACE docs first:
docs/gtm/capability-map.mddocs/gtm/client-conversion-pipeline.mddocs/gtm/linkedin-content-calendar.mddocs/gtm/core-engineering-work-conversion.mdFor wiki work, inspect:
index.mdlog.mdBefore drafting posts or website copy, create one or more of:
Good examples from this session:
docs/gtm/fowt-engineering-scope.mddocs/gtm/installation-analysis-method-note.mddocs/gtm/marine-terminal-engineering-scope.mddocs/gtm/lng-berth-operability-framing.mdEvery new scope note should include:
Examples learned here:
For new domains, create:
For marine terminals, the proven cluster was:
lng2026-tp04-shipping-marine-port-operations.mdlng-marine-terminal-engineering.mdlng-berth-operability.mdlng-transfer-system-envelope.mdfsru-marine-terminal-interface.mdUpdate:
index.mdlog.mdAfter the engineering artifact exists, update GTM docs with engineering-first wording:
capability-summary.mdcapability-map.mdclient-conversion-pipeline.mdlinkedin-content-calendar.mdcore-engineering-work-conversion.mdUse parallel subagents when the two tracks are independent:
Then use parallel subagents again for derived scope-note drafting.
Recommended pairings:
For any new capability area, produce this ladder:
knowledge/wikis/* may be gitignored; remember future commits may require git add -fIf the user says “add this external post/page to GTM,” the safest, highest-value response is: