task-observer

Logs skill improvement observations during task-oriented agent sessions.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/lacsousa/mediclaw-system --skill task-observer-lacsousa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: task-observer
Source: https://github.com/lacsousa/mediclaw-system/tree/main/.claude/skills/task-observer
Command: npx skills add https://github.com/lacsousa/mediclaw-system --skill task-observer-lacsousa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Insights about how AI skills could be improved get lost between sessions because nobody captures them during real work. This Skill provides a persistent observation layer that watches multi-step tasks, user corrections, and methodology discussions, then logs reusable patterns to a persistent observation log so they can later be turned into new or improved skills. ## Core Features & Use Cases - Continuous Observation Logging: Silently appends structured observations (Issue, Suggested improvement, Principle) to a persistent log file throughout the entire session, including post-task feedback phases. - Collision-Safe Numbering: Enforces pre-write assertion and post-write verification with automatic renumbering to prevent duplicate observation IDs when parallel sessions write to the same log. - Skill Taxonomy Guidance: Classifies observations as open-source or internal skill candidates, with rules for attribution, licensing, lean content, and confidentiality boundaries. - Use Case: During a long agentic workflow, a user corrects the agent's output twice in the same way. The Skill logs the correction pattern immediately, and at the weekly review the pattern becomes a new enforcement rule in an existing skill. ## Quick Start Invoke the task-observer skill at the start of any session where you will use tools and produce deliverables, and add its activation instruction to your CLAUDE.md file.

Frequently Asked Questions about task-observer

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

FAQPage Schema
How do I make the task-observer skill activate reliably every session?▼

Add an activation instruction to your CLAUDE.md or equivalent configuration file telling the agent to invoke task-observer at the start of any task-oriented session. Description-level matching alone is not enforceable, so the structural trigger acts as the primary mechanism.

How does the observation log prevent duplicate observation numbers?▼

Before writing, the skill greps the log for the highest existing observation number and asserts the proposed number is unused. After appending, it re-reads the log and renumbers via sed if a parallel session caused a collision, closing the time-of-check-to-time-of-use race.

What is the difference between open-source and internal skills in this taxonomy?▼

Open-source skills are client-agnostic, methodology-driven, and require author attribution, a licence, and a feedback channel. Internal skills contain client-specific or proprietary context, need no attribution or licence, and can be less formally structured.

When should observations not be logged?▼

Do not log one-off corrections that do not generalise, preferences already captured in existing skills, tool bugs unrelated to methodology, or observations requiring proprietary client information for an open-source skill. Observation is also inactive during casual non-task conversation.

Does task-observer work in web-based chat without filesystem access?▼

Yes, but it shifts into handoff doc mode where the user manages the observation log files manually. With filesystem access, the agent appends to the log directly using shell commands.