using-sentinel

Coordinate security engagements and write assessment artifacts as markdown and HTML.

8|2|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/wangdongzuopin/sentinel-skill --skill using-sentinel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-sentinel
Source: https://github.com/wangdongzuopin/sentinel-skill/tree/main/skills/AuditSentry/using-sentinel
Command: npx skills add https://github.com/wangdongzuopin/sentinel-skill --skill using-sentinel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides coordination of security engagements (audit, pentest, CTF, CVE research) with post-engagement artifacts written to sentinel-report as markdown and HTML.

Core Features & Use Cases

  • Post-engagement artifact workflow: After audit/pentest/frontend work completes, sentinel-report artifacts must be generated and written as .md and .html.
  • Sequential task chaining: Guides the user to open sentinel-report/SKILL.md and write sentinel-security-assessment.md + sentinel-security-assessment.html.
  • Enforced reporting discipline: Prevents chat-only findings and ensures formal, shareable reports.

Quick Start

Use the audit/pentest workflow to chain to sentinel-report and generate the required artifacts.

Frequently Asked Questions about using-sentinel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I auto-generate markdown and HTML security reports after a pentest?

Security engagement coordination chains sequential audit, pentest, and CVE research tasks, then enforces a closing gate step to generate formal post-engagement artifacts. It ensures findings are written as shareable markdown and HTML files rather than stopping at chat-only output.

How do I coordinate multi-host security workflows for audit and CTF tasks?

Multi-host security workflows for audit and CTF tasks are coordinated through sequential task chaining across hosts. The workflow enforces a closing gate step that guides users to generate required post-engagement security assessment artifacts in markdown and HTML formats.

Why does my security audit workflow stop at chat-only findings without generating files?

Security audit workflows stop at chat-only findings when they lack enforced reporting discipline. A proper post-engagement workflow requires opening the sentinel-report SKILL.md and writing sentinel-security-assessment markdown and HTML artifacts to satisfy formal generation requirements.

Can I use automated reporting for CVE research and frontend security assessments?

Yes, automated reporting applies to CVE research and frontend security assessments. The workflow coordinates these engagements and generates post-engagement artifacts, writing security assessment output to both markdown and HTML files.

What is the required step to close a security engagement and generate assessment artifacts?

The required step to close a security engagement is opening the sentinel-report SKILL.md to follow the closing gate. This enforces the generation of sentinel-security-assessment.md and sentinel-security-assessment.html artifacts.