skeek

Identify and annotate security vulnerabilities and quality flaws in software code.

8|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/smile13241324/aemacs --skill skeek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skeek
Source: https://github.com/smile13241324/aemacs/tree/main/.agents/skills/skeek
Command: npx skills add https://github.com/smile13241324/aemacs --skill skeek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Skeek identifies security vulnerabilities and logic flaws in codebases, enabling teams to detect and remediate risks before they reach production.

Core Features & Use Cases

  • Automated security review for bugs and weaknesses in software projects.
  • Generates a risk ledger with severity and location to guide remediation.
  • Integrates into code-review and CI workflows for continuous safety checks.

Quick Start

Run Skeek on the target repository to begin a thorough risk assessment.

Frequently Asked Questions about skeek

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

FAQPage Schema
How do I automate security review and bug detection for my codebase?

Automated security review is performed by running static analysis on the target repository to identify critical bugs and security weaknesses, outputting a structured risk ledger with severity and file references.

Can I integrate static analysis into CI workflows for continuous code vetting?

Yes, static analysis integrates into CI workflows and code-review processes to perform continuous safety checks, validating inputs against defined rules to catch vulnerabilities before production.

Does this static analysis tool support multiple programming languages?

Static analysis applies across languages for code reviews and CI vetting, focusing on identifying critical bugs and security weaknesses without being limited to a specific programming environment.

What is a risk ledger and how does it guide vulnerability remediation?

A risk ledger is a structured output detailing security vulnerabilities with severity levels and file references, providing remediation notes to guide teams in fixing detected code flaws.

What is the best way to identify security flaws and quality flaws during code reviews?

The best way to identify security and quality flaws is applying static analysis that annotates vulnerabilities across languages, validating inputs against rules to generate a comprehensive risk ledger.

What are the limitations of using automated static analysis for security review?

Automated static analysis validates inputs strictly against its defined rules and focuses on critical bugs, meaning it may not catch complex logic flaws outside its rule scope without manual review.