[BUG] Deleted skill keeps appearing in scheduled task context (Cowork)

Resolved 💬 3 comments Opened Apr 16, 2026 by 1987heartbreaker-beep Closed Apr 20, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

In Claude Cowork (Desktop), a custom skill that was deleted from
Customize > Skills continues to appear in the "Skills" section of
the context panel every time a scheduled task runs.

Verified the skill is gone from:

  • Customize > Skills (deleted)
  • Project folder and hidden subfolders (not found)
  • Project memory (empty)
  • Scheduled task prompt (no reference)

The deleted skill "agrinote-weekly-weather-v2" loads automatically
on every scheduled task execution despite being removed everywhere accessible.

What Should Happen?

Deleted skills should not appear in any task context after deletion.

Error Messages/Logs

Steps to Reproduce

  1. Install a custom skill in Customize > Skills in Cowork
  2. Create a scheduled task linked to a Cowork project
  3. Delete the custom skill from Customize > Skills
  4. Run the scheduled task (manually or automatically)
  5. Check the right panel context during execution

→ The deleted skill reappears under "Skills" section

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

Claude 1.2773.0 (884b37) 2026-04-15T14:32:09.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

This issue only occurs during scheduled task execution.
The skill does NOT appear in the project context panel
when running tasks manually from the project view.

Recreating the scheduled task from scratch does not resolve the issue.
The behavior is fully reproducible on every scheduled run.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗