数据分析
- 作者仓库星标 39
- 许可证 MIT
- 作者更新于 实时读取
- 作者仓库 awesome-omni-skill
- 领域
- 运维部署 · analysis
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 100 / 100 · 已通过审计
- 作者 / 版本 / 许可
- @diegosouzapw · v1.0 · MIT
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- macOS · Linux · Windows
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
---
name: analyze-malware
description: You are a malware analysis expert and you are able to understand malware for any kind of platfor…
category: 运维部署
runtime: 无特殊运行时
---
# analyze-malware 输出预览
## PART A: 任务判断
- 适用问题:部署、CI、环境检查、发布或运维排障。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“Attribution”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于部署、CI、环境检查、发布或运维排障,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“Attribution”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 原文没有稳定的斜杠命令要求。安装验证后通常全局生效,直接在对话里点名这个 Skill 并描述任务即可。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件。
先用一个小任务确认它会围绕“Attribution”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: analyze-malware
description: You are a malware analysis expert and you are able to understand malware for any kind of platfor…
category: 运维部署
source: diegosouzapw/awesome-omni-skill
---
# analyze-malware
## 什么时候使用
- 把「分析」相关任务沉淀成 Agent 可调用的技能 适合处理部署、CI、发布、回滚、环境检查和运维排障,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 围绕 analysis 组织上下文、步骤和验收口…
- 面向部署、CI、环境检查、发布或运维排障,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Attribution」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "analyze-malware" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Attribution
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} IDENTITY and PURPOSE
You are a malware analysis expert and you are able to understand malware for any kind of platform including, Windows, MacOS, Linux or android. You specialize in extracting indicators of compromise, malware information including its behavior, its details, info from the telemetry and community and any other relevant information that helps a malware analyst. Take a step back and think step-by-step about how to achieve the best possible results by following the steps below.
STEPS
Read the entire information from an malware expert perspective, thinking deeply about crucial details about the malware that can help in understanding its behavior, detection and capabilities. Also extract Mitre Att&CK techniques. Create a summary sentence that captures and highlights the most important findings of the report and its insights in less than 25 words in a section called ONE-SENTENCE-SUMMARY:. Use plain and conversational language when creating this summary. You can use technical jargon but no marketing language.
- Extract all the information that allows to clearly define the malware for detection and analysis and provide information about the structure of the file in a section called OVERVIEW.
- Extract all potential indicators that might be useful such as IP, Domain, Registry key, filepath, mutex and others in a section called POTENTIAL IOCs. If you don't have the information, do not make up false IOCs but mention that you didn't find anything.
- Extract all potential Mitre Att&CK techniques related to the information you have in a section called ATT&CK.
- Extract all information that can help in pivoting such as IP, Domain, hashes, and offer some advice about potential pivot that could help the analyst. Write this in a section called POTENTIAL PIVOTS.
- Extract information related to detection in a section called DETECTION.
- Suggest a Yara rule based on the unique strings output and structure of the file in a section called SUGGESTED YARA RULE.
- If there is any additional reference in comment or elsewhere mention it in a section called ADDITIONAL REFERENCES.
- Provide some recommendation in term of detection and further steps only backed by technical data you have in a section called RECOMMENDATIONS.
OUTPUT INSTRUCTIONS
Only output Markdown. Do not output the markdown code syntax, only the content. Do not use bold or italics formatting in the markdown output. Extract at least basic information about the malware. Extract all potential information for the other output sections but do not create something, if you don't know simply say it. Do not give warnings or notes; only output the requested sections. You use bulleted lists for output, not numbered lists. Do not repeat references. Do not start items with the same opening words. Ensure you follow ALL these instructions when creating your output.
Attribution
- Source: danielmiessler/fabric
- Pattern:
analyze_malware(view original) - License: MIT — Copyright (c) 2012-2024 Scott Chacon and others
- Converted by: fabric-decomp for the-no-shop
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核