tradecraft-pivot-decisions
Decide what to do next after a result — the branching logic that turns a single outcome into the next lead. Load whenever a step just finished (success, partial, or dead end) and it's unclear where to go: "what now", "I got a shell/creds/a hash", "this didn't work", triaging which of several leads t
v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/tradecraft-pivot-decisionsWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packageeb24f631…260ab66b
eb24f6312479…3c4d260ab66b1 file · 1.6 KBScanLowno findings
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/tradecraft/tradecraft-pivot-decisions@ee0e0c5
On this page
When it applies
A step just produced a result and you must choose the next action instead of blindly running the next tool. Applies after every meaningful step — this is what keeps an engagement adaptive.
Why it works
Value comes from routing on evidence: a result changes the probability and payoff of every other
lead. Making the routing explicit (what the result unlocks, what it rules out) avoids both
tunnel-vision and aimless scanning, and produces the decision + rationale entries the Attack
Map is built from.
Method
- Classify the result: confirmed / partial / blocked / failed. Record it as the lead's
status. - Ask what it unlocks (route by artifact — the signal → skill map):
- creds / hash → crack or spray (
network-credential-cracking,network-password-spraying) - a shell → enumerate & escalate (
privesc-enumeration→privesc-*) - SSRF / file read → reach internal services, metadata (
cloud-imds-ssrf,web-ssrf) - a token / key → what identity does it become? (
cloud-iam-privesc,ad-*) - two small bugs that combine →
exploit-chaining - internal foothold →
network-pivoting-tunneling, map the graph (tradecraft-attack-path-mapping)
- creds / hash → crack or spray (
- Score the candidates: impact toward the objective × likelihood × cost/noise; pick the top one.
- On a dead end, don't just stop: record why (so it's not retried), then fall back to the next-best lead from the scenario. "Blocked by infra" ≠ "not vulnerable" — say which.
- Update the plan: re-order remaining leads; note the new pivot. Then act on the single top lead.
Gotchas
- Sunk cost: abandon a low-yield lead even after effort if a better one appeared.
- "It failed" without a reason is a lost lesson — always record the mechanism of the failure.
- Chasing novelty over objective: the next move is the one that best advances the stated goal.
Verify success
After each result there is a recorded decision (status + rationale) and exactly one chosen next lead that advances the objective — the engagement never stalls on "what now".
References
OODA loop applied to offense; MITRE ATT&CK tactic transitions; the exploit-chaining skill.
Files in this version
- SKILL.md2.7 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | eb24f631 | Signed | – |
More from NoorQureshi
All from this publisherMore in Network, wireless and telecom
See the category- performing-network-packet-capture-analysismukul975/performing-network-packet-capture-analysis4
- network-segmentation-reviewsecurityskills/network-segmentation-review3
- performing-ssl-stripping-attackmukul975/performing-ssl-stripping-attack3
- implementing-next-generation-firewall-with-palo-altomukul975/implementing-next-generation-firewall-with-palo-alto3
- configuring-zscaler-private-access-for-ztnamukul975/configuring-zscaler-private-access-for-ztna3
- implementing-canary-tokens-for-network-intrusionmukul975/implementing-canary-tokens-for-network-intrusion3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login