420company
420company/artemis
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/420company/artemis --skill audit-software命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
This skill should be used when the user asks to "call the Spotify Ads API", "create a Spotify ad campaign", "manage Spotify ads", "pull Spotify ad reports", "set up ad sets or ads", "upload ad assets", "target audiences on Spotify", "check campaign status", "get ad account info", "look up API schema or fields", "check what targeting options exist", or asks about Spotify advertising endpoints, request/response formats, enum values, or authentication.
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
Accessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
基于 SOC 职业分类
正在显示 SKILL.md
| name | audit-software |
| disable-model-invocation | true |
| argument-hint | [software_name] [location_or_department] |
| description | Audit software inventory across devices using ZDX data for compliance and vulnerability assessment. |
Audit software: $ARGUMENTS
Extract:
zdx_list_software()
```text
If a specific software was requested, filter the results.
## Step 3: Drill Into Specific Software
For targeted investigation:
```text
zdx_get_software_details(software_key="<software_name_and_version>")
```text
Check version distribution across devices.
## Step 4: Check Device Details
For devices with outdated or concerning software:
```text
zdx_list_devices(search="<filter>")
zdx_get_device(device_id="<id>")
```text
## Step 5: Present Report
**ALWAYS present data in HTML tables** in the chat response using `<table>`, `<thead>`, `<tbody>`, `<tr>`, `<th>`, `<td>` tags with inline styling. Use color-coded rows: green (current), yellow (one version behind), red (EOL/vulnerable).
Include:
1. **Software inventory table** (software name, version(s), device count, status, risk level)
2. **Compliance summary table** (up to date count/%, one version behind count/%, EOL count/%)
3. **Detailed analysis** explaining the compliance posture, version distribution patterns, and geographic concentration of outdated software
4. **Security assessment** for each EOL/vulnerable entry with risk explanation
5. **Next steps / resolution** prioritized by risk:
- Critical (EOL): immediate upgrade plan, MDM push, maintenance windows
- High (known CVEs): cross-reference with CVE data, prioritize sensitive departments
- Medium (one version behind): schedule automated updates
- Low (current): verify auto-update policies
## Step 6: Generate Downloadable Artifacts — MANDATORY
**You MUST create BOTH files. Do NOT skip the HTML page.**
1. **Word document** (`software_inventory_audit_<date>.docx`): Executive summary, full inventory table, security findings, prioritized recommendations.
2. **Interactive HTML page** (`software_inventory_audit_<date>.html`): Use the complete HTML template from the `zdx-audit-software-inventory` skill. The file must be fully functional with working search bar, sortable columns, filter dropdowns, color-coded rows, summary dashboard, and CSV export button. All CSS and JavaScript inline — no external dependencies. Populate the `<tbody>` with one `<tr>` per software entry from the collected data.
**Write both files to disk and provide the file paths to the user.**