Execute one test/attack and record outcome, evidence, and severity. Tool use is runtime-selected.
Scanned 9/24/2026
npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill execute-probe --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Execute Probe?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/yogsoth-ai-execute-probe)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: execute-probe
description: "Execute one test/attack and record outcome, evidence, and severity. Tool use is runtime-selected."
---
# execute-probe
## Purpose
Execute one test or attack and record outcome, evidence, and severity.
## Input contract
```yaml
required: [probe_spec, target, success_and_failure_conditions]
optional: [tool_context, severity_scale]
constraints: [probe scope and interpretation rule must be fixed before execution]
```
## Procedure
1. Verify target and probe conditions.
2. Run the probe and capture observations.
3. Classify outcome against the predeclared conditions.
If probe observations and protocol deviations are recorded, consider `classify-falsification-verdict` as the next tactic.
## Output contract
```yaml
produces: [probe_record, observations, outcome, severity]
delta_fields: [findings, evidence_updates, uncertainties, decisions]
```
## Quality gates
- Preserve raw observation, execution context, and interpretation separately.
## Failure and counterexamples
An unavailable tool or inconclusive observation is uncertainty, not a passing probe.
## Provenance map
- resolved: probe-execution
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!