observe-skill

Log skill execution outcomes to a per-skill runs.md file.

6|1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/securityfortech/hacking-skills --skill observe-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: observe-skill
Source: https://github.com/securityfortech/hacking-skills/tree/main/skills/meta/observe-skill
Command: npx skills add https://github.com/securityfortech/hacking-skills --skill observe-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps track and analyze the performance of other skills, identifying what works and what fails in real-world execution to improve reliability.

Core Features & Use Cases

  • Outcome Logging: Records the success, partial success, or failure of a skill run.
  • Detailed Reporting: Captures date, task description, what worked, what failed, and error messages.
  • Use Case: After running a complex vulnerability scanning skill, use observe-skill to log that it successfully identified a specific vulnerability but failed to parse the output correctly, providing details for later refinement.

Quick Start

Log the outcome of the last skill run, noting that it worked.

Frequently Asked Questions about observe-skill

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

FAQPage Schema
How do I log skill execution outcomes for post-run analysis?

Log skill execution outcomes by recording the date, task description, skill name, and outcome status to a per-skill runs.md file within an observations directory for post-execution analysis.

What is skill performance observation and when do I need it?

Skill performance observation tracks what works and what fails in real-world execution. You need it when analyzing reliability issues and identifying specific successes, failures, and error messages for refinement.

How do I track debugging errors and failures from automated tasks?

Track debugging errors by capturing verbatim error messages, specific failures, and outcome status—whether success, partial, or fail—into a structured log file for later analysis and improvement.

Can I log partial successes when a task only partially works?

Yes, you can log partial successes. The outcome logging captures success, partial success, and failure states, recording both what worked and what failed alongside verbatim error messages.

What's the best way to record verbatim error messages from a failed run?

Record verbatim error messages by logging them with the date, task description, skill name, and outcome status into a dedicated runs.md file, preserving exact error text for debugging and refinement.

Does this logging approach work without external dependencies?

Yes, this logging approach works without external dependencies. It writes outcome details directly to a per-skill runs.md log file within an observations directory using standard file operations.