Update to Aikido Security

{
  "description": "List, count, summarize, or triage security issues from the Aikido security feed. Use when the user asks about Aikido findings, vulnerabilities, leaked secrets, SAST/IaC/SCA results, cloud or container security issues, or EOL/license/malware alerts surfaced by Aikido.",
  "included_files": [],
  "name": "aikido-issues",
  "skill_md_contents": "---\nname: aikido-issues\ndescription: List, count, summarize, or triage security issues from the Aikido security feed. Use when the user asks about Aikido findings, vulnerabilities, leaked secrets, SAST/IaC/SCA results, cloud or container security issues, or EOL/license/malware alerts surfaced by Aikido.\n---\n\nWhen listing Aikido feed issues:\n\n1. Use **aikido-mcp:aikido_issues_list**\n2. Call it when the user wants to list, show, count, or summarize Aikido feed issues.\n3. Pass scope fields only when the user (or workspace context) supplies them: `cloud_name`, `repo_name`, `repo_branch_name`, `vm_name`, `domain_name`, `container_name`, `team_name`, `workspace_name`.\n4. Optional `issue_types` (array): `open_source`, `leaked_secret`, `cloud`, `sast`, `iac`, `surface_monitoring`, `malware`, `eol`, `mobile`, `docker_container`, `cloud_instance`, `scm_security`, `license`, `ai_pentest` — e.g. include `leaked_secret` for secrets. Omit when no category filter is needed.\n5. SLA filters (booleans): set `out_of_sla: true` when the user wants issues that are past their SLA, or `sla_due_soon: true` for issues approaching their SLA deadline.\n6. Pagination: use numeric `page` only when the user needs more than the first page of results (zero-indexed). Only 25 findings are reported per page. Report to the user if there are more findings on following pages.\n7. Detail lookup: pass `issue_id` (string) to fetch one issue with more detail than the list returns. Use it when the user asks to dig into, explain, triage or fix a specific issue, or names an issue by its ID. `issue_id` overrides every other filter — the call returns that single issue, so do not combine it with scope, type, SLA or pagination fields.\n8. Present each issue exactly in this form (increment `#`):\n   ```\n   Issue #1: <issue_title>\n    - ID: <issue_id>\n    - Issue type: <issue_type>\n    - Severity: <issue_severity> (<issue_severity_label>)\n    - Remediation: <issue_remediation>\n   ```\n   Add extra bullets when the field is relevant, e.g. `File: <issue_file> (line <issue_start_line>)`, `Location: <location.type> <location.name> (<location.branch_name>)`, `Issue link: <issue_link>`, `SLA due date: <issue_remediate_by_date>`.\n9. For an `issue_id` lookup, keep the same format and then summarize the extra fields the detailed response carries.\n\n\nIf the Aikido MCP server is not available or fails, inform the user:\n\n> The Aikido MCP server is required for Aikido feed issues but is not available.\n> Install it following the setup guide at [reference.md](../scan/reference.md), or run the **setup** skill, then retry.\n"
}