
Analyzing campaign attribution evidence
Campaign attribution analysis involves systematically evaluating evidence to determine which threat actor or group is responsible for a cybe
- Scripts
- None
- Platforms
- Claude Code, Codex, Cursor
- GitHub stars
- 72
- Last commit
- 18 days ago
- License
- Apache-2.0
- Listing updated
- today
When your agent uses it
Campaign attribution analysis involves systematically evaluating evidence to determine which threat actor or group is responsible for a cyber operation. This skill covers collecting and weighting attr
From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.
What it can access
From a static check of its 1 file (9 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.
Install
This skill ships in the asi plugin. In Claude Code, add the marketplace and install the plugin (it may include other skills too):
/plugin marketplace add plurigrid/asi
/plugin install asi@asiOr copy only this skill to ~/.claude/skills/analyzing-campaign-attribution-evidence:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/plurigrid/asi.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/analyzing-campaign-attribution-evidence &&
cp -R "$tmp/plugins/asi/skills/analyzing-campaign-attribution-evidence" ~/.claude/skills/analyzing-campaign-attribution-evidence &&
rm -rf "$tmp"For one project only, put the folder in .claude/skills/analyzing-campaign-attribution-evidence inside it instead.
Copy the skill folder to ~/.agents/skills/analyzing-campaign-attribution-evidence to use it in every repository:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/plurigrid/asi.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/analyzing-campaign-attribution-evidence &&
cp -R "$tmp/plugins/asi/skills/analyzing-campaign-attribution-evidence" ~/.agents/skills/analyzing-campaign-attribution-evidence &&
rm -rf "$tmp"For one repository only, put the folder in .agents/skills/analyzing-campaign-attribution-evidence inside it instead.
Copy the skill folder to ~/.cursor/skills/analyzing-campaign-attribution-evidence to use it in every project:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/plurigrid/asi.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/analyzing-campaign-attribution-evidence &&
cp -R "$tmp/plugins/asi/skills/analyzing-campaign-attribution-evidence" ~/.cursor/skills/analyzing-campaign-attribution-evidence &&
rm -rf "$tmp"For one project only, put the folder in .cursor/skills/analyzing-campaign-attribution-evidence inside it instead.
Run in a terminal (add --scope workspace to install it for the current workspace only):
gemini skills install https://github.com/plurigrid/asi.git --path plugins/asi/skills/analyzing-campaign-attribution-evidenceOr copy the folder to ~/.gemini/skills/analyzing-campaign-attribution-evidence yourself.
For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/analyzing-campaign-attribution-evidence:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/plurigrid/asi.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/analyzing-campaign-attribution-evidence &&
cp -R "$tmp/plugins/asi/skills/analyzing-campaign-attribution-evidence" ~/.copilot/skills/analyzing-campaign-attribution-evidence &&
rm -rf "$tmp"For one project only, put the folder in .github/skills/analyzing-campaign-attribution-evidence inside it instead.
Get the folder:
git clone --depth 1 https://github.com/plurigrid/asi.gitThen copy asi/plugins/asi/skills/analyzing-campaign-attribution-evidence into your agent's skills folder as analyzing-campaign-attribution-evidence. Agents that support SKILL.md read one folder per skill.
Analyzing campaign attribution evidence FAQ
How do I install Analyzing campaign attribution evidence in Claude Code?
Copy the skill folder from GitHub to ~/.claude/skills/analyzing-campaign-attribution-evidence to use it in all your projects, or to .claude/skills/analyzing-campaign-attribution-evidence in one project. Or install the asi plugin, which includes it: /plugin marketplace add plurigrid/asi, then /plugin install asi@asi.
Does Analyzing campaign attribution evidence run scripts?
No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.
Which AI agents can use Analyzing campaign attribution evidence?
Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.
What are the best alternatives to Analyzing campaign attribution evidence?
The closest alternatives to Analyzing campaign attribution evidence are Ad campaign analyzer, Prd v08 changelog as marketing, Prd v08 marketing ops handoff, Product led SEO and SEO matomo.
More from plurigrid/asi

Org-agenda-like transient views for ASI skill orchestration via nbb/squint + Emacs hydra
- Open source
- 72 GitHub stars

Connect and stream from OpenBCI Cyton/Daisy via USB dongle, including first-time radio channel pairing
- Open source
- 72 GitHub stars

Hypothesis-Test Loops via REPL for Exploratory Abductive Inference with Gay.jl colors
- Open source
- 72 GitHub stars

Layer 4 Learning and Pattern Extraction for Cognitive Surrogate Systems
- Open source
- 72 GitHub stars

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration
- Open source
- 72 GitHub stars

Automated code review for pull requests using specialized review patterns
- Open source
- 72 GitHub stars
- Developer tools
Alternatives to Analyzing campaign attribution evidence

Ad campaign analyzer
SkillUse this skill when the user shares ad campaign performance data and asks what to cut, scale, or test
- Open source
- 41.3K GitHub stars
- Marketing and SEO

Design the changelog as a distribution surface bridging engineering releases (DEP-/FEA-) to marketing channels (GTM-) during PRD v0.8 Deploy
- Open source
- 179 GitHub stars
- Marketing and SEO

Define lifecycle stages and marketing → sales / CSM handoff rules for leads captured by GTM channels during PRD v0.8 Deployment & Ops
- Open source
- 179 GitHub stars
- Marketing and SEO

Product led SEO
SkillUse when asked to "product-led SEO", "programmatic SEO", "build programmatic pages", "organic acquisition for product", "decide if SEO is wo
- Open source
- 59 GitHub stars
- Marketing and SEO


SEO agentic
SkillAudit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI
- Open source
- 30.2K GitHub stars
- Marketing and SEO
