<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Skill Poison field notes</title><link>https://skillpoison.com</link><description>Editorial guides on the security of reusable AI agent skills.</description><item><title>What is skill poisoning?</title><link>https://skillpoison.com/guides/skill-poisoning.html</link><guid>https://skillpoison.com/guides/skill-poisoning.html</guid><description>A complete starting point: what gets poisoned, how a skill gains influence, and which boundaries determine the outcome.</description></item><item><title>The anatomy of an agent skill</title><link>https://skillpoison.com/guides/skill-anatomy.html</link><guid>https://skillpoison.com/guides/skill-anatomy.html</guid><description>Read the package as a map of possible influence: metadata, instructions, references, scripts, assets, and dependencies.</description></item><item><title>Instructions, data, and authority</title><link>https://skillpoison.com/guides/instruction-boundaries.html</link><guid>https://skillpoison.com/guides/instruction-boundaries.html</guid><description>How to reason about skill text that asks for more than the user’s task—and why enforcement must survive a bad interpretation.</description></item><item><title>Poisoning discovery and skill selection</title><link>https://skillpoison.com/guides/metadata-selection.html</link><guid>https://skillpoison.com/guides/metadata-selection.html</guid><description>Risk can start before the main skill instructions load. Review descriptions, retrieval, and the planner’s choice of package.</description></item><item><title>Hidden risk in references and assets</title><link>https://skillpoison.com/guides/references-assets.html</link><guid>https://skillpoison.com/guides/references-assets.html</guid><description>A skill’s supporting files can introduce instructions, destinations, or content that the entry file does not reveal.</description></item><item><title>Scripts and dependencies inside skills</title><link>https://skillpoison.com/guides/scripts-dependencies.html</link><guid>https://skillpoison.com/guides/scripts-dependencies.html</guid><description>Inspect the code path separately from the instruction path. A skill can introduce software behavior as well as natural-language guidance.</description></item><item><title>Provenance, pinning, and updates</title><link>https://skillpoison.com/guides/updates-provenance.html</link><guid>https://skillpoison.com/guides/updates-provenance.html</guid><description>How to preserve the meaning of a review when package content, dependencies, or the execution environment changes.</description></item><item><title>Backdoors in model-bearing skills</title><link>https://skillpoison.com/guides/model-artifact-backdoors.html</link><guid>https://skillpoison.com/guides/model-artifact-backdoors.html</guid><description>Some skills bundle learned artifacts. Reviewing their instructions and scripts may not reveal the behavior encoded inside a model.</description></item><item><title>When skills combine: composition risk</title><link>https://skillpoison.com/guides/skill-composition.html</link><guid>https://skillpoison.com/guides/skill-composition.html</guid><description>A workflow can create a risk that is difficult to see when each skill is reviewed in isolation.</description></item><item><title>Threat-model a skill before you install it</title><link>https://skillpoison.com/guides/threat-model.html</link><guid>https://skillpoison.com/guides/threat-model.html</guid><description>An actionable map of influence, assets, actors, permissions, and recovery for one real skill workflow.</description></item><item><title>Least privilege for installed skills</title><link>https://skillpoison.com/guides/least-privilege.html</link><guid>https://skillpoison.com/guides/least-privilege.html</guid><description>Design a permission profile that allows the task to work while limiting what a poisoned skill could reach.</description></item><item><title>A repeatable skill admission review</title><link>https://skillpoison.com/guides/reviewing-skills.html</link><guid>https://skillpoison.com/guides/reviewing-skills.html</guid><description>A practical sequence for deciding what to approve, what evidence to retain, and when to keep a skill out of a sensitive workflow.</description></item><item><title>The skill poisoning defense checklist</title><link>https://skillpoison.com/guides/defense-checklist.html</link><guid>https://skillpoison.com/guides/defense-checklist.html</guid><description>A concrete review baseline across package content, authority, execution, updates, and incident readiness.</description></item><item><title>Detection and testing for poisoned skills</title><link>https://skillpoison.com/guides/detection-and-testing.html</link><guid>https://skillpoison.com/guides/detection-and-testing.html</guid><description>Measure the complete path from loaded content to observable effect, while keeping evaluations isolated from production.</description></item><item><title>How to read skill poisoning research</title><link>https://skillpoison.com/guides/benchmark-reading.html</link><guid>https://skillpoison.com/guides/benchmark-reading.html</guid><description>A guide to interpreting attack success rates, datasets, defenses, and benchmark claims without turning one result into a universal conclusion.</description></item><item><title>Evaluate the complete skill lifecycle</title><link>https://skillpoison.com/guides/lifecycle-evaluation.html</link><guid>https://skillpoison.com/guides/lifecycle-evaluation.html</guid><description>A review matrix from repository admission to evolution, with observable questions at every stage.</description></item><item><title>Publish skills that are easier to trust</title><link>https://skillpoison.com/guides/publishing-skills.html</link><guid>https://skillpoison.com/guides/publishing-skills.html</guid><description>Practical authoring choices that help downstream reviewers understand scope, permissions, dependencies, and changes.</description></item><item><title>Respond to a suspected poisoned skill</title><link>https://skillpoison.com/guides/incident-response.html</link><guid>https://skillpoison.com/guides/incident-response.html</guid><description>Contain the package, preserve evidence, distinguish attempts from effects, and recover from a reviewed state.</description></item><item><title>When experience becomes a poisoned skill</title><link>https://skillpoison.com/guides/experience-to-skill-poisoning.html</link><guid>https://skillpoison.com/guides/experience-to-skill-poisoning.html</guid><description>Why a reusable rule needs its own review, even when the task that produced it appeared successful.</description></item><item><title>From a description to an action</title><link>https://skillpoison.com/guides/metadata-end-to-end.html</link><guid>https://skillpoison.com/guides/metadata-end-to-end.html</guid><description>Review the entire selection chain instead of treating skill metadata as harmless catalog text.</description></item><item><title>When documentation becomes executable output</title><link>https://skillpoison.com/guides/documentation-to-execution.html</link><guid>https://skillpoison.com/guides/documentation-to-execution.html</guid><description>A guide to reviewing examples and templates that a coding agent may copy into a real workflow.</description></item><item><title>Why a scanner can look strong and still fail</title><link>https://skillpoison.com/guides/scanner-benchmark-design.html</link><guid>https://skillpoison.com/guides/scanner-benchmark-design.html</guid><description>Source overlap, false alarms, and evaluation choices can change what a headline detection score means.</description></item><item><title>Read the version, not just the headline</title><link>https://skillpoison.com/guides/reading-research-revisions.html</link><guid>https://skillpoison.com/guides/reading-research-revisions.html</guid><description>A research librarian’s checklist for changing titles, revised taxonomies, and conference status.</description></item><item><title>What marketplace studies can actually tell us</title><link>https://skillpoison.com/guides/marketplace-evidence.html</link><guid>https://skillpoison.com/guides/marketplace-evidence.html</guid><description>Separate vulnerable packages, confirmed malicious behavior, and deliberately assembled test collections.</description></item><item><title>The prerequisite trap: when setup becomes the attack</title><link>https://skillpoison.com/guides/prerequisite-traps.html</link><guid>https://skillpoison.com/guides/prerequisite-traps.html</guid><description>Review installation requests and human handoffs as carefully as the actions an agent executes itself.</description></item><item><title>A clean result with missing coverage</title><link>https://skillpoison.com/guides/scanner-coverage-gaps.html</link><guid>https://skillpoison.com/guides/scanner-coverage-gaps.html</guid><description>Learn to read skipped files, parser failures, truncated content, and mismatched package inventories.</description></item><item><title>Poisoned advice and output integrity</title><link>https://skillpoison.com/guides/output-integrity.html</link><guid>https://skillpoison.com/guides/output-integrity.html</guid><description>An agent can finish the visible task while steering recommendations, recipients, or decisions away from the user’s goal.</description></item><item><title>When one skill supplies the pretext for another</title><link>https://skillpoison.com/guides/cross-skill-pretext.html</link><guid>https://skillpoison.com/guides/cross-skill-pretext.html</guid><description>Follow evidence, state, and authority across a skill chain when no single file explains the final action.</description></item><item><title>What model-internal detectors can and cannot show</title><link>https://skillpoison.com/guides/model-internal-detection.html</link><guid>https://skillpoison.com/guides/model-internal-detection.html</guid><description>Read detection research in terms of observed signals, benchmark conditions, and deployment limits.</description></item><item><title>From scanner warning to defensible finding</title><link>https://skillpoison.com/guides/scanner-evidence-levels.html</link><guid>https://skillpoison.com/guides/scanner-evidence-levels.html</guid><description>How to write a review result that does not confuse a heuristic, a trace, an attempted action, and impact.</description></item><item><title>When one session leaves instructions for the next</title><link>https://skillpoison.com/guides/cross-session-skill-artifacts.html</link><guid>https://skillpoison.com/guides/cross-session-skill-artifacts.html</guid><description>Trace the authority of persistent files that connect multiple skills after chat history is cleared.</description></item><item><title>A skill can do the task and an extra action</title><link>https://skillpoison.com/guides/dual-purpose-skill-review.html</link><guid>https://skillpoison.com/guides/dual-purpose-skill-review.html</guid><description>Inspect the entire package and its imports when a useful result could hide a separate side effect.</description></item></channel></rss>