菜单
Productlane (productlane.com). Use this skill for ANY Productlane request — reading, creating, updating, and deleting data. Whenever a task involves Productlane, use this skill instead of calling the API directly.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/oomol-lab/skills --skill oo-productlane命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | oo-productlane |
| description | Productlane (productlane.com). Use this skill for ANY Productlane request — reading, creating, updating, and deleting data. Whenever a task involves Productlane, use this skill instead of calling the API directly. |
| allowed-tools | ["Bash(oo *)"] |
| metadata | {"title":"Productlane","author":"OOMOL","version":"1.0.0","services":["productlane"],"icon":"https://static.oomol.com/logo/third-party/productlane.svg"} |
Operate Productlane through your OOMOL-connected account. This skill calls the productlane connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.
Assume the user has already installed the oo CLI, signed in, and connected Productlane. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.
1. Inspect the contract to get the authoritative input/output schema before building a payload:
oo connector schema "productlane" --action "<action_name>"
2. Run the action with a JSON payload that matches the input schema:
oo connector run "productlane" --action "<action_name>" --data '<json>' --json
--data takes a JSON object string or @path/to/file.json; omit it to send {}.{ "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.
create_company — Create a company in the connected Productlane workspace. [write]create_contact — Create a contact in the connected Productlane workspace. [write]delete_company — Soft-delete a Productlane company by ID. [destructive]delete_contact — Soft-delete a Productlane contact by ID. [destructive]get_authenticated_identity — Get the authenticated Productlane API key identity, granted scopes, and Linear team selection.get_company — Get a Productlane company by ID.get_contact — Get a Productlane contact by ID.list_companies — List Productlane companies with cursor pagination and documented filters.list_contacts — List Productlane contacts with cursor pagination and documented filters.update_company — Update a Productlane company by ID. [write]update_contact — Update a Productlane contact by ID. [write][write] change Productlane state — confirm the exact payload and effect with the user before running.[destructive] remove or overwrite data — always confirm the target and get explicit approval first.These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.
oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux
irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell
Not signed in / authentication error — sign in to your OOMOL account once:
oo auth login
scope_missing / credential_expired / app_not_ready / app_not_found — Productlane is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:
https://console.oomol.com/app-connections?provider=productlane
HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.