Shameless plug: in case someone finds this requiring too many tokens, we shared the recipe on how we built our own in house audit skill so that it can easily be replicated and tuned to different environments https://www.synthesia.io/post/automating-code-security-revie...
Hi Cloudflare people, if you are reading this. Please clean up your Cloudflare. Skills. There are way too many skills for the platform. You should consolidate all of your skills into a single skill and route everything thru that skill. The way it is right now pollutes our context window.
The descriptions are shorter now, but they used to read like ads. The skill split still feels arbitrary. You turn on what you think you need, then hit some Cloudflare task that needs another skill and have to go fetch it.
I don’t get why these need to be separate. One skill with progressive disclosure already handles this. That’s kind of the point.
Tip for security professionals using LLMs: audit skills that explicitly frame the task as security research sometimes trigger refusals from the top OpenAI and Anthropic models because they guard against misuse. What works for me: separate skills for bug classes (and bugs in general) without the security framing, plus another skill that combines their findings to spot security bugs.
If you're a security professional, go through their validation. You won't get the security refusals anymore. Well... you'll still get the occasional downgrade from Fable, but not the "oh no, I can't do exploits for you" breaks.
Did you open the repo? There's a subdirectory with two dozens of files, around 300Kb of text.
Storing/visualizing small text changes over time as revisions is exactly what Git is excellent at, how else would you keep track of updates to the prompts?
Probably to save their skin if agent starts to do some unexpected things and bringing havoc. But I doubt that OpenAI models with normal subscription, for example, wont even work with this skill.
https://github.com/cloudflare/skills/tree/main/skills
I don’t get why these need to be separate. One skill with progressive disclosure already handles this. That’s kind of the point.
I forwarded this to the right person, and it sounds like it's being worked on. Thanks!
For a todo cli. That doesn’t work.
Storing/visualizing small text changes over time as revisions is exactly what Git is excellent at, how else would you keep track of updates to the prompts?
I dont? because prompts are not a thing that are ever needed to be tracked lol.