{"version":"2.1.280","anchor":"propose-skills-tool-now-validates-proposal-targets-before-th","canonical_anchor":"propose-skills-tool-now-validates-proposal-targets-before-th","heading":"propose_skills tool now validates proposal targets before the read-before-improve check","tier":"internal","area":"Skills","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/propose-skills-tool-now-validates-proposal-targets-before-th","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### propose_skills tool now validates proposal targets before the read-before-improve check\n\nThe propose_skills tool now checks that proposals are valid before running its existing freshness checks\n\n**Unclear.** The finding does not say what specifically makes a proposal fail this new validation.\n\n**What**\n\nThe `propose_skills` tool (used to submit proposed skills, which are packaged instructions Claude Code can follow for a task) now runs an extra validation pass over all proposals before it gets to the existing check that requires a skill to have been read recently before it can be improved. If this new check fails, the tool returns an error (error code 2) with a message explaining the problem.\n\nThis builds on the tool's existing description-length cap, which previously enforced descriptions under 200 characters (never exceeding 1024).\n\n**Why**\n\nCatching invalid proposals earlier means the tool can reject bad input with a clear message before spending time on the later freshness check, giving faster and more direct feedback when a proposal is malformed.\n\n- Area: Skills\n- Names: `propose_skills`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}