Skip to content
cccskills
FreePublished on GitHub

observe-skill

Logs the outcome of a skill execution to observations/<skill-name>/runs.md. Trigger on: "log this run", "skill worked", "skill failed", "this didn't work", "log the outcome", "record this", "note that", or after any skill completes with a clear success, partial, or failure outcome. Creates the observations file if it does not exist, then appends an entry with date, task description, skill used, outcome, what worked, what failed, and any error messages observed.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md3.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Observe Skill

Purpose

Track how skills perform in practice. A skill that works in theory may miss steps, use outdated payloads, or fire on the wrong triggers in real-world conditions. This skill captures that gap by recording execution outcomes to a per-skill log file.

Trigger Conditions

Activate this skill when the user says any of:

  • "log this run"
  • "skill worked" / "that worked"
  • "skill failed" / "that didn't work" / "this didn't work"
  • "log the outcome"
  • "record this run"
  • After any skill completes and the user describes a result (success, partial, fail)

Methodology

  1. Identify which skill was just used — ask if unclear. The skill name must match a directory name under skills/.
  2. Determine the outcome — success (goal achieved), partial (some steps worked, some didn't), or fail (skill produced no useful result).
  3. Collect details:
    • Date (today's date)
    • Task description (what was the user trying to do?)
    • What specifically worked (payloads, steps, tools that produced results)
    • What specifically failed (steps that produced no result, wrong output, or errors)
    • Any error messages or unexpected responses verbatim
  4. Write the entry — append to observations/<skill-name>/runs.md. Create the file and directory if they don't exist.
  5. Confirm — show the user the appended entry.

Entry Format

---
date: YYYY-MM-DD
skill: <skill-name>
task: <one-line description of what was attempted>
outcome: success | partial | fail
what_worked: |
  <describe what steps, payloads, or approaches produced results>
what_failed: |
  <describe what steps or payloads did not work>
errors: |
  <paste any error messages or unexpected responses>
notes: |
  <any additional context — target type, environment quirks, etc.>
---

Example Interaction

User: "log this run — bola-idor worked, I found a sequential integer ID on /api/orders and was able to read other users' orders using my own session token"

Response: Creates or appends to observations/bola-idor/runs.md:

---
date: 2026-03-14
skill: bola-idor
task: Test /api/orders endpoint for horizontal IDOR using sequential integer ID
outcome: success
what_worked: |
  Sequential integer IDs confirmed. Substituting victim's order ID (attacker ID +/- 1-10)
  returned full order details including name, address, and payment last4. Tested with
  attacker's Bearer token — no ownership check.
what_failed: |
  UUID endpoint /api/orders/uuid was not vulnerable — UUIDs not guessable.
errors: |
  None.
notes: |
  REST API, no GraphQL. /api/v1/ also vulnerable. /api/v2/ returns 403 on cross-user ID.
---

Fix Patterns

This is a meta-skill — it has no fix patterns. It generates data that other skills (especially /amend-skill) consume.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Exploit pervasive logical flaws in Multi-Factor Authentication (MFA/2FA) implementations to bypass the secondary authentication challenge entirely. Techniques include response manipulation, referal spoofing, token reuse, and predictable backup codes.

The English summary is being prepared. Showing the original description.

ShulkwiSEC/bb-huge23Updated Jul 11, 2026

401/403 bypass playbook. Use when encountering access-denied responses on admin panels, API endpoints, or restricted paths. Covers path manipulation, HTTP method tampering, header injection, protocol downgrade, and automated bypass tools.

The English summary is being prepared. Showing the original description.

ShulkwiSEC/bb-huge23Updated Jul 11, 2026

Complete PortSwigger deep-dive with exact payloads for every lab variant including zero-day techniques

The English summary is being prepared. Showing the original description.

ShulkwiSEC/bb-huge23Updated Jul 11, 2026

Active Directory ACL abuse playbook. Use when exploiting misconfigured AD permissions including GenericAll, WriteDACL, DCSync rights, shadow credentials, LAPS reading, GPO abuse, and BloodHound-guided attack paths.

The English summary is being prepared. Showing the original description.

ShulkwiSEC/bb-huge23Updated Jul 11, 2026

Execute AS-REP Roasting to extract and crack the NTLM hashes of Active Directory user accounts that have the "Do not require Kerberos preauthentication" flag explicitly enabled. This attack generates a recoverable Ticket Granting Ticket (TGT) without requiring the attacker to authenticate first.

The English summary is being prepared. Showing the original description.

ShulkwiSEC/bb-huge23Updated Jul 11, 2026

AD Certificate Services attack playbook. Use when targeting misconfigured AD CS for privilege escalation via ESC1-ESC13 template abuse, NTLM relay to enrollment, CA officer abuse, and certificate-based persistence.

The English summary is being prepared. Showing the original description.

ShulkwiSEC/bb-huge23Updated Jul 11, 2026

See all skills by ShulkwiSEC

Report a problem with this skill