security-checklist

Analyze Excel security checklist items for GitHub Enterprise support.

3|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/theomonfort/theomonfort --skill security-checklist-theomonfort
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-checklist
Source: https://github.com/theomonfort/theomonfort/tree/main/.github/skills/security-checklist
Command: npx skills add https://github.com/theomonfort/theomonfort --skill security-checklist-theomonfort

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the analysis of a security checklist Excel file by interactively guiding sheet selection, items column identification, and output column designation to determine GitHub Enterprise support for each item using the official FAQ and reference checklists.

Core Features & Use Cases

  • Interactive sheet selection to identify the relevant worksheet containing the security checklist.
  • Auto-detection of the items column and contextual metadata (category, priority, notes) to map each item to GitHub Enterprise capabilities.
  • Classification of each item as ✅ Supported, ⚠️ Partially Supported, ❌ Not Supported, or ❓ Unclear, with per-item justifications and citations in a generated output.

Quick Start

Run the interactive setup to select the sheet, identify the items column, choose the output column, and specify the customer name to configure the analysis.

Frequently Asked Questions about security-checklist

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

FAQPage Schema
How do I automate security checklist analysis for GitHub Enterprise support?

Automate security checklist analysis by interactively selecting the Excel worksheet, detecting the items column, and classifying each countermeasure against the GitHub Customer Security Trust FAQ to generate structured per-item verdicts.

Can I write GitHub Enterprise compliance verdicts back to an Excel file without losing existing data?

Yes, you can write GitHub Enterprise compliance verdicts back to Excel while preserving existing data, appending per-item classifications like Supported, Partially Supported, or Not Supported directly to the designated output column.

What is the process for mapping security countermeasures to GitHub Enterprise capabilities?

Mapping security countermeasures to GitHub Enterprise capabilities involves auto-detecting the items column and contextual metadata, then comparing each item against official FAQ and reference checklists to produce a justified classification.

Does this tool classify security checklist items as fully supported or partially supported?

Yes, the tool classifies security checklist items as Supported, Partially Supported, Not Supported, or Unclear, providing per-item justifications and citations based on the GitHub Customer Security Trust FAQ.

How do I configure an Excel security checklist to assess GitHub Enterprise compliance?

To configure Excel security checklist assessment, run the interactive setup to select the relevant sheet, identify the items column, choose the output column, and specify the customer name for the analysis.

Why does my security checklist need an output column designated before analysis?

Designating an output column before security checklist analysis ensures the tool has a specific target location to write per-item GitHub Enterprise support verdicts back into the Excel file without overwriting existing contextual metadata.