task-observer

Logs skill improvement observations during work sessions into a structured Markdown observation log.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/jeremybrasher/grokbot-skills --skill task-observer-jeremybrasher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: task-observer
Source: https://github.com/jeremybrasher/grokbot-skills/tree/main/skills/task-observer
Command: npx skills add https://github.com/jeremybrasher/grokbot-skills --skill task-observer-jeremybrasher

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? AI agent skills stay frozen after creation: corrections, preferences, and workflow insights discovered during real work are lost between sessions, and nobody systematically identifies which new skills should be built. This Skill runs alongside every work session, captures those signals as structured observation files, and drives a review cycle that turns them into skill improvements. ## Core Features & Use Cases - Continuous observation logging: Watches tool-using sessions for user corrections, recurring patterns, and methodology gaps, writing one Markdown file with YAML frontmatter per observation into a persistent observation-log directory. - Skill candidate discovery: Flags repeating workflows that no existing skill covers and proposes new skills, validating targets and checking sibling skill families before writing. - Scheduled review cycle: Tracks a last-review-date file, offers or runs a comprehensive review of open observations, and stages approved skill updates in a skill-updates folder without editing live skills. - Use Case: A consultant with 30 installed skills notices the agent keeps making the same report-formatting mistake. The observer logs the correction, a later review confirms the pattern, and a staged update to the reporting skill is presented for approval. ## Quick Start Install the skill folder with its references and scripts, add the activation block to your CLAUDE.md, then ask the agent at the end of a work session: any observations logged?

Frequently Asked Questions about task-observer

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

FAQPage Schema
How do I make my AI agent skills improve over time?▼

Install a meta-skill that observes work sessions and logs corrections, patterns, and gaps as structured observation files. A periodic review then applies validated observations as staged updates to your existing skills, so the library improves from real usage rather than manual audits.

How does the task-observer skill log observations?▼

It writes one Markdown file per observation into skill-observations/observation-log/, with YAML frontmatter for status, skill, and date, plus a body of issue, improvement, and principle. Writes happen in the same turn as the observed friction, with mandatory checkpoints after every third completed todo.

Does task-observer work outside Claude Cowork?▼

Yes. It runs in Claude Code with a pinned absolute workspace path, and in web or mobile chat via handoff-doc mode where observations are delivered as a structured document. Users have also reported integrations with Openclaw, Hermes, and Codex setups.

What happens if the observation log scan returns nothing?▼

An empty parse of a non-empty log is treated as a broken command, not as a finding of no observations. The skill counts files independently of the parse and halts with an error if files exist but no headers were extracted.

When should I not use an observation-logging meta-skill?▼

Skip it for casual conversation and one-shot factual questions with no tools or deliverables. It also refuses to invent backlogs, write skills from imagination, or promote a single unvalidated observation into a live skill rule.