Individual skill
final-report
Final engagement report generation — executive summary, technical report, findings aggregation, attack path narrative, detection gap matrix, remediation roadmap.
packages/decepticon/decepticon/skills/standard/decepticon/final-report/SKILL.md
Source commit df879550544d36b6b1e69062f05adae28537adf2
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 6,565
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- ai Repository topic
- cybersecurity Repository topic
- hacking Repository topic
- langchain Repository topic
- langgraph Repository topic
- llm Repository topic
- generative-ai Repository topic
- pentesting Repository topic
- pentest Repository topic
- engineering Derived category
Declared tags are partial or unavailable.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Final Engagement Report Generation
The selected workflow defines when a report is needed, its audience and artifact
paths. This skill provides optional writing templates and evidence interpretation;
it does not start a reporting phase, create directories or require unavailable
planning documents. Select only sections supported by the assignment and evidence.
A report with no confirmed vulnerabilities is valid; do not invent entries to fill
the examples or treat the template's pentest title as a required engagement type.
## Finding metadata interpretation
For workflow version 2 inspect the artifact registry and committed finding UUIDs;
publish one `report/security-assessment-report.md` with executive conclusions,
scope and limits, findings links, observed paths, Info/coverage and remediation.