メニュー
Investigate Pi Security findings - list, locate, explain, summarize, or compare findings by FND-XXX ID, UUID, or Pi finding URL. Read-only; uses Pi's hosted MCP tools as evidence.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Submit a security report to Pi as inline Markdown with a .md or .markdown filename, after explicit user confirmation. Reports the queued ingestion workflow state truthfully.
Fetch existing Pi remediation guidance for a finding or an SBOM package, and optionally prepare a missing package remediation plan after explicit user confirmation.
Review Pi Security posture - threat-model application and section context combined with Code Gatekeeper PR and issue reviews. Read-only; uses Pi's hosted MCP tools as evidence.
Get repo-specific Pi secure-development guidance for a concrete engineering task, optionally query tenant knowledge for a specific ambiguity, and record playbook feedback after confirmation.
Start a Pi Security design review from a supported Confluence or Notion document URL or from inline Markdown, after explicit user confirmation. No attachments, local files, or binaries.
| name | investigate-finding |
| description | Investigate Pi Security findings - list, locate, explain, summarize, or compare findings by FND-XXX ID, UUID, or Pi finding URL. Read-only; uses Pi's hosted MCP tools as evidence. |
Use this skill when the user wants to list, locate, explain, summarize, compare, or investigate security findings recorded in Pi Security.
pi_findings_list - lists findings visible to the authenticated tenant user, with filters and pagination.pi_finding_get - gets one finding. ref accepts a FND-XXX display ID, a finding UUID, or a Pi finding URL.pi_remediation_plan_fetch - optional. Use only when the user asks how to fix a finding and existing remediation guidance is relevant. For deeper remediation work, use the remediation-guidance skill instead.FND-XXX, UUID, or a Pi finding URL), call pi_finding_get with ref set to that reference exactly as given. Do not rewrite or "correct" identifiers.pi_findings_list and narrow with filters that match the request (for example severity or status). Fetch only as many pages as the question requires.