AnalystAIPack vs docs.dev

It will happily tell you to "check the file for anything malicious," suggest a plugin that does not exist, or skip the one step that actually matters.

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no...

About AnalystAIPack

It will happily tell you to "check the file for anything malicious," suggest a plugin that does not exist, or skip the one step that actually matters. What it lacks is the analyst's working knowledge: which Volatility 3 plugin to run on a memory image, how to reach a packer's original entry point, how to turn a recovered C2 config into a Sigma rule, and, just as important, when not to trust a result. It is an open, Apache-2.0 library of 118 agent skills for malware analysis, reverse engineering, and threat hunting, and it is now public on GitHub.

About docs.dev

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no platform fee, no metered AI. Reviews, branches, and rollbacks come free, because it is just git. Your content in their database, and an export button you hope works when you leave. Writing AI is the agent you already have; reader-facing AI runs on your Workers AI.