external-feedback-triage
Evaluate external technical feedback before acting. Use for reviews, scanner findings, blog advice, model suggestions, and recommendations whose applicability or evidence is uncertain.
v2026.11.13-21cd5683 installs+3 in 7 days39 StarsMITsynced 11 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/external-feedback-triageWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Packagee867dbe2…5b9e6ada
e867dbe25837…f1c15b9e6ada1 file · 2.0 KBScanLowno findings
Sourcegithub.com/AeonDave/malskill/tree/main/knowledge/external-feedback-triage@21cd568
Turn feedback into an evidence-backed disposition and complete the warranted work. A correct observation does not automatically justify the proposed remedy; a poor remedy does not invalidate the underlying defect.
Triage and act
- Separate the claims: identify the observed behavior, inferred cause/impact, and proposed change. Split mixed feedback into independently checkable items; consolidate duplicates without counting them as corroboration.
- Locate the current context: inspect the affected code or artifact, contract, version, configuration and existing decisions. Check nearby dependencies when they matter; a valid finding need not sit on a changed line.
- Test the claim: use the smallest meaningful inspection, reproduction or test. Assess impact and confidence separately; distinguish defects, preferences and optional improvements. A severity label or authoritative tone is not evidence. If direct verification is unavailable, preserve that uncertainty.
- Choose the disposition: use the table below. Check the proposed remedy against the actual cause, compatibility, edge cases and maintenance cost. Resolve contradictory suggestions against evidence and project requirements.
- Finish accepted work: apply the smallest sufficient fix within the task's authorization, then verify the affected behavior and relevant regressions. Continue independent accepted items while another needs clarification. Do not stop at a proposed patch when implementation is already requested.
- Report the outcome: state what was applied, adapted, deferred or rejected, why, and what evidence or check supports it. Name unresolved risk without inflating it. For several items, a compact disposition table can help.
| Disposition | Use when |
|---|---|
| Apply | The finding and remedy fit the current evidence, contract and task. |
| Adapt | The issue is real but the proposed fix breaks another requirement or misses the cause. |
| Defer | A potentially useful item needs evidence/access, belongs to later work, or exceeds the current task; give the revisit condition. |
| Reject | The claim is contradicted, inapplicable, or the suggested change has no justified benefit; cite the relevant evidence. |
| Clarify | A missing requirement or unresolved choice materially changes correctness, scope or authorization and cannot be established locally. |
Existing authorization remains valid. A request to review alone does not authorize implementation; a request to fix supported findings does not require another blanket approval. Honour explicit style preferences as preferences without inventing a technical defect.
Check the source-specific trap
| Input | Check that changes the decision |
|---|---|
| Code review | The requirement and affected behavior, including callers; avoid unrelated cleanup disguised as a necessary fix. |
| Scanner | Actual dependency/build, enabled code path and relevant preconditions; banners or a negative probe alone cannot settle applicability. |
| Advisory or PoC | Affected branch/configuration, backports, trigger and side effects; inspect external code before considering execution. |
| Model suggestion | Whether the referenced file, API and behavior actually exist. |
| Blog or tool advice | The documented version, environment and tradeoff behind the recommendation. |
Push back with evidence when a suggestion changes the wrong version, masks a failing test, weakens the contract, or solves a different problem. Do not dismiss a necessary boundary or abstraction merely because it has only one current caller.
Load evidence-before-claims when evidence is disputed or a claim exceeds the observation. Load verification-before-completion before claiming an applied fix complete. Use known-problem-hint-research when external evidence is the missing piece.
Files in this version
- SKILL.md4.2 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.11.13-21cd568 | Nov 13, 2026 | 21cd568 | e867dbe2 | Signed | – |
More from AeonDave
All from this publisherMore in Reporting and compliance
See the category- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
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