When testing the latest version of the skill in Lovable, after running the setup skill, it decided to go cowboy mode and run its own integration for the app based on assumed patterns. This meant it skipped the SDKs entirely.
Let's be explicit in the setup skill and instruct the AI on completion that it should run the billing-integration skill or prompt the user to run it.
This is what Lovable suggested to add:
- Telling billing-setup to hand off to billing-integration — would have basically prevented it.
This is the real fix. Skills are most reliable when they explicitly declare their boundaries and successors. Something like, at the end of billing-setup/SKILL.md:
> Next step
> This skill only configures products and pricing. Do not write integration code yourself — endpoints, SDK shapes, and auth headers are easy to guess wrong. Run the billing-integration skill (or ask the user to: npx skills add credyt/ai-tools then "run the billing-integration skill"). If that skill is not installed, stop and ask the user before proceeding.
Two things make that work:
An explicit prohibition ("do not improvise") is much stronger than an implicit one. Agents will fill silence with confident guesses; a sentence telling them not to short-circuits that.
A named successor + install command turns "I should look for something" into a concrete next tool call. Much harder to skip.
You could also add a one-liner at the top of billing-integration confirming it's the canonical path ("This is the only supported way to wire Credyt into application code — do not hand-roll fetch calls or guess endpoints"), so even if the agent stumbles into it directly it gets the same signal.
Bonus: if billing-setup had said "the SDK is @credyt/api-client" in passing, even an off-script agent would have at least installed the SDK instead of inventing https://api.credyt.ai + X-CREDYT-API-KEY from thin air.
When testing the latest version of the skill in Lovable, after running the setup skill, it decided to go cowboy mode and run its own integration for the app based on assumed patterns. This meant it skipped the SDKs entirely.
Let's be explicit in the setup skill and instruct the AI on completion that it should run the
billing-integrationskill or prompt the user to run it.This is what Lovable suggested to add: