vigilia

Aggregate defensive ward spell outputs into a unified readiness verdict.

Updated May 20, 2026
One-click install
npx skills add https://github.com/watmin/datamancy.dev --skill vigilia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vigilia
Source: https://github.com/watmin/datamancy.dev/tree/main/vigilia
Command: npx skills add https://github.com/watmin/datamancy.dev --skill vigilia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vigilia aggregates the outputs of all inward defensive wards to give practitioners a single, coherent view of a target's readiness.

Core Features & Use Cases

  • Aggregates per-spell findings from the grimoire's defensive wards (intueri, purgare, conformare, solvere, secare, mora, excusare) into a unified report.
  • Executes wards in parallel and surfaces an overall convergence verdict with L1/L2 severities to guide remediation.
  • Use Case: Cast Vigilia on a code target to compare the target against multiple concerns (naming, structure, dead code, craft, state, and waste) in one pass.

Quick Start

Cast Vigilia on a target or directory to generate an aggregated report from all inward wards.

Frequently Asked Questions about vigilia

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

FAQPage Schema
What is an aggregated defensive ward assessment for code analysis?

Aggregated defensive ward assessment collects outputs from multiple inward code analysis spells to evaluate target readiness. It executes parallel checks across concerns like naming, structure, and dead code, presenting a unified convergence verdict with prioritized remediation guidance.

How do I run parallel code analysis checks across multiple risk concerns?

Run parallel code analysis by casting an aggregation spell on a target directory. This executes all defensive wards simultaneously across naming, structure, dead code, craft, state, and waste concerns, collecting per-spell findings into a single convergence report.

How are risk assessment findings prioritized in an aggregated code report?

Risk assessment findings are prioritized by severity levels L1 and L2. The aggregation process surfaces urgent L1 findings from upstream wards first, guiding immediate remediation before addressing less critical L2 issues in the overall convergence verdict.

Does the grimoire defensive ward aggregation require any external dependencies?

No external dependencies are required for grimoire defensive ward aggregation. The spell operates independently to collect and synthesize outputs from internal wards like intueri, purgare, conformare, solvere, secare, mora, and excusare into a unified readiness report.

What's the best way to survey surrounding risk after running defensive ward spells?

The best way to survey surrounding risk is performing circumspicere after aggregating ward outputs. This surveys the broader risk landscape around the target, complementing the inward defensive findings with outward risk awareness for comprehensive readiness assessment.

Can I assess a directory target for multiple code quality concerns in one pass?

Yes, you can assess a directory target in one pass by casting an aggregation spell. It compares the target against multiple concerns simultaneously—naming, structure, dead code, craft, state, and waste—generating a single aggregated report with per-spell findings.