<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Claude-Code-Skills on Start AI Tools - Presented by Intent Solutions</title><link>https://startaitools.com/tags/claude-code-skills/</link><description>Recent content in Claude-Code-Skills on Start AI Tools - Presented by Intent Solutions</description><generator>Hugo</generator><language>en-US</language><copyright>Intent Solutions. All rights reserved.</copyright><lastBuildDate>Mon, 04 May 2026 07:20:07 -0600</lastBuildDate><atom:link href="https://startaitools.com/tags/claude-code-skills/index.xml" rel="self" type="application/rss+xml"/><item><title>An Anti-Slop Framework Found Three Bugs Inside Itself on Day One</title><link>https://startaitools.com/posts/anti-slop-framework-found-three-bugs-inside-itself/</link><pubDate>Sun, 03 May 2026 08:00:00 -0500</pubDate><guid>https://startaitools.com/posts/anti-slop-framework-found-three-bugs-inside-itself/</guid><description>&lt;p&gt;A framework whose entire purpose is to catch silent failures in AI-generated OSS contributions is the worst possible place to host silent failures. That tension is the spine of this case study. The framework in question is &lt;code&gt;contributing-clanker&lt;/code&gt;, an installable Claude Code skill that walks an OSS contribution lifecycle through 41 deterministic gates spanning seven phases and 62 enumerated AI-slop failure modes. It shipped at v0.1.0 around 20:20 local time. By the end of the same day it was at v0.1.2 — because the first real qualifying flow against a third-party upstream (&lt;code&gt;secureblue/secureblue#2138&lt;/code&gt;) surfaced &lt;strong&gt;three categorically named bash/CLI silent-failure modes&lt;/strong&gt; inside the framework itself, plus a minor scoping bug already patched in v0.1.1.&lt;/p&gt;</description></item></channel></rss>