菜单
Launch, install, verify, or help operate the Outbound PM Operations Hub Jira dashboard. Use when the user asks to open the Jira dashboard, start the dashboard, fix live ticket fetching, share or install the dashboard package, or work with the Outbound PM operating hub.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Orchestrate production-ready LiveStacks solutions from PRDs, working PRDs, or minimal business-first inputs such as industry, pain point, category, Oracle feature mapping, deployment target, and implementation notes. Use when Codex needs to turn a business or industry pain point, PRD, workbook-style brief, or solution concept into a secure, portable, Oracle Database-first LiveStacks application bundle with architecture, data design, ORDS-mediated APIs, container artifacts, implementation guidance, documentation, and customer rebuild instructions.
Create clean distributable ZIP archives from files or project directories while excluding macOS metadata, Python caches, VCS metadata, editor temporary files, and other generated artifacts. Use when packaging a project, source tree, handoff bundle, deployment archive, or any ZIP that must not contain .DS_Store, __MACOSX, __pycache__, resource forks, or similar clutter.
Disable Polly retrieval and memory writes for the current local Git clone while preserving its canonical repository and quiet-mode settings. Use when a repository should no longer participate in Polly or was enabled unintentionally.
Enable Polly for the current clone or fork and configure its canonical upstream GitHub repository using local git config. Use when opting a repository into Polly or correcting fork-to-upstream memory resolution.
Diagnose Polly enrollment, repository enablement, secure token availability, canonical repository resolution, and server health. Use when Polly context is missing or setup needs verification.
Save a durable developer-only project memory in Polly without tying it to the current Codex session or sharing it with collaborators. Use when the user wants a personal decision, hypothesis, reminder, preference, or continuity note available in future sessions for the same canonical repository.
| name | jira-dashboard |
| description | Launch, install, verify, or help operate the Outbound PM Operations Hub Jira dashboard. Use when the user asks to open the Jira dashboard, start the dashboard, fix live ticket fetching, share or install the dashboard package, or work with the Outbound PM operating hub. |
Always launch the dashboard through the local Python server before telling the user it is ready. Never direct users to open index.html with a file:// URL, because live Jira fetching requires the local server API.
Run:
python3 "$HOME/.codex/skills/jira-dashboard/scripts/launch_dashboard.py"
The launcher:
~/Documents/Codex if it is missing.localhost, preferring port 8901.http://localhost:<port>/ URL.scripts/launch_dashboard.py every time this skill is used for opening or troubleshooting the dashboard.http://localhost:<port>/ URL for all browser checks.file://.../index.html URL, move them to the printed localhost URL.mcp-atlassian in ~/.codex/config.toml.The bundled dashboard zip lives at:
assets/OutboundPM-operations-dashboard-v13-operating-hub.zip
The default installed folder is:
~/Documents/Codex/OutboundPM-operations-dashboard-v13-operating-hub
If a user asks to share the dashboard with teammates, share the full jira-dashboard skill folder or the packaged skill zip. Teammates still need their own Jira MCP credentials and VPN access for live Jira data.