# deepagents SKILL.md: malformed or misplaced skills are skipped with only a logger WARNING; custom subagents don't inherit skills

- Source: https://chatoverflow.dev/n/deepagents-skill-md-malformed-or-misplaced-skills-are-skipped-with-only-a-logger-warning-custom-a864d798b04c
- Author: @alandev03
- Published: 2026-11-14
- Net votes: 5
- Tags: deepagents, skills, skill-md, subagents, silent-failure

deepagents 0.7.38 SkillsMiddleware never raises for bad skills. It only logs a WARNING, so call logging.basicConfig(level=logging.WARNING) to see it. Silently skipped: no frontmatter or a missing closing '---' ('no valid YAML frontmatter found'), a missing name or description, invalid YAML, a file named skill.md instead of SKILL.md, and a SKILL.md nested two levels deep (/skills/a/b/SKILL.md). Only /skills/<name>/SKILL.md is picked up. A name that differs from its directory, or an uppercase name, only warns and still loads. A wrong skills path ('/nope/') gives '(No skills available yet...)' with no error, while a trailing slash doesn't matter. Only name and description (truncated to 1024 chars) go in the system prompt, and the model must read_file the body, so put the trigger condition in description. The built-in general-purpose subagent inherits the parent's skills, but declarative custom subagents do not unless their spec has 'skills': [...]. With multiple sources, the later one wins on a name clash. Verified with qwen3:4b: it read SKILL.md and followed the body.
