sc-orchestrator

Coordinate end-to-end security scanning across multiple phase-specific tools.

56|5|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ersinkoc/security-check --skill sc-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sc-orchestrator
Source: https://github.com/ersinkoc/security-check/tree/main/skills/sc-orchestrator
Command: npx skills add https://github.com/ersinkoc/security-check --skill sc-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Master orchestration that coordinates the entire 4-phase security scanning pipeline, ensuring smooth execution, error handling, and results aggregation across all sub-skills.

Core Features & Use Cases

  • Central coordination of reconnaissance, dependency audits, language-specific vulnerability checks, verification, and reporting
  • Automatic orchestration of phase transitions, error handling, and progress tracking
  • Diff-mode support and robust artifact generation for security reporting

Quick Start

Issue a command such as 'run security check' to start the full four-phase pipeline

Frequently Asked Questions about sc-orchestrator

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

FAQPage Schema
How do I automate end-to-end security scanning across multiple programming languages?

End-to-end security scanning is coordinated by orchestrating reconnaissance, dependency audits, and language-specific vulnerability checks into a consolidated SECURITY-REPORT.md.

What is an orchestrator pipeline for vulnerability scanning?

A vulnerability scanning orchestrator pipeline coordinates distinct scanning phases, managing phase transitions, error handling, and progress logging to aggregate results from multiple security checks.

Can I run security checks on only the changed code using diff-mode?

Diff-mode security checks are supported, allowing the scanning pipeline to target only changed code sections while maintaining robust artifact generation and progress logging.

Does the security scanning pipeline require specific output directories?

The security scanning pipeline requires designated output directories like security-report to store progress logs, phase artifacts, and the final consolidated security report.

What happens if a phase-specific vulnerability check fails during the scan?

If a vulnerability check fails, the orchestrator applies robust error handling to manage the exception, log the progress, and continue coordinating the remaining security scanning phases.

How do I generate a comprehensive security report from multiple scanning tools?

Generate a comprehensive security report by orchestrating reconnaissance, dependency audits, and verification phases, aggregating all findings into a final SECURITY-REPORT.md file.