reviewing-agent-effectiveness

Diagnose agent enforcement mechanisms and report FIRED, NOT FIRED, or NOT APPLICABLE per mechanism.

2|1|Updated Apr 13, 2025
One-click install
npx skills add https://github.com/Jose-Luis-Nunez/FitnessApp --skill reviewing-agent-effectiveness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-agent-effectiveness
Source: https://github.com/Jose-Luis-Nunez/FitnessApp/tree/main/.cursor/skills/reviewing-agent-effectiveness
Command: npx skills add https://github.com/Jose-Luis-Nunez/FitnessApp --skill reviewing-agent-effectiveness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose which agent enforcement mechanisms (rules, hooks, skills) fired during a task and which did not, producing a per-mechanism FIRED / NOT FIRED / NOT APPLICABLE report.

Core Features & Use Cases

  • Audits enforcement mechanisms across L2, L3, L5, and pre-commit layers to identify gaps.
  • Generates a per-task report detailing which mechanisms activated and which did not, enabling audits and improvements.
  • Useful after non-trivial implementations, refactors, or audits to evaluate whether enforcements gripped as intended.

Quick Start

Run the reviewing-agent-effectiveness skill after completing a task to generate the enforcement firing report.

Frequently Asked Questions about reviewing-agent-effectiveness

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

FAQPage Schema
How do I audit which agent enforcement mechanisms fired during a task?

You can audit agent enforcement mechanisms by generating a per-task report that details which rules, hooks, and skills activated. This diagnostic produces a FIRED, NOT FIRED, or NOT APPLICABLE status for each mechanism.

What is an agent enforcement firing report used for?

An agent enforcement firing report is used to evaluate whether rules, skills, and hooks gripped as intended during non-trivial implementations. It identifies enforcement gaps across L2, L3, L5, and pre-commit layers to guide improvements.

When should I run an audit of agent rules and hook performance?

You should run an audit of agent rules and hook performance after completing non-trivial implementations, refactors, or audits. This timing ensures you accurately assess whether Always-Apply Rules and Pre-Commit Hooks performed as expected.

Can I check if my pre-commit hook and stop hook performed correctly across tasks?

Yes, you can check pre-commit hook and stop hook performance across tasks. The audit evaluates these specific enforcement layers alongside Always-Apply Rules and Skills, reporting their activation status.

Why do my agent enforcement rules not fire during an implementation?

Agent enforcement rules might not fire due to gaps in the enforcement configuration across L2, L3, L5, or pre-commit layers. An audit report identifies which mechanisms are NOT FIRED, guiding configuration improvements.