How can we help?
Pick a skill with a useful promise, bring your ingredients and choose how to use it.
← Return to Plan a trip, day by day
Where did you get stuck?
Connect or use copy instead
Keep your selected skill. Check endpoint reachability and workspace permission. First test list_recipes. A remote assistant cannot reach localhost.
Open connection instructions →Other assistant setup paths
Documented setup: Cursor, Codex, and Claude / Claude Code. These guides are not a claim that a current output has been tested in every host. Copy-prompt use stays available without MCP.
The essentials
Where do I start?
Browse the skill library. Each skill explains its promised result, ingredients and limitations. Customize and copy its prompt into your AI app, or choose Use with MCP to retrieve the same published instructions in Claude. These are delivery choices for one skill.
Older outcome links keep their original contracts during migration. An older outcome with a similar name is not automatically the same skill. Skills retain their own installation guidance.
Where will my finished result appear?
In your AI conversation. LazyCoder supplies instructions; your assistant asks for missing facts and generates the draft. Any example shown on a skill page is an illustration, not your result. No preview or independent review is claimed when one is unavailable.
Does the short ID install a slash command?
No. Copy the skill’s starter request. It names the exact ID and version for get_recipe and asks the assistant to confirm the publication release. Skill IDs and older /lc- identifiers help retrieval; this connector does not register slash commands.
My assistant can’t find LazyCoder. What should I do?
Check that the connector address ends in /mcp, LazyCoder is enabled in this conversation and your workspace allows custom connectors. Ask for list_recipes, then get_recipe with an exact returned ID and version. Confirm a tool retrieval happened; a response from memory does not prove a connection.
Claude remote connectors need a publicly reachable server. They cannot reach your localhost. For a local build, use Claude Code on the same computer as explained in the connection guide.
What if I don’t have all the ingredients?
Required ingredients are marked on the skill. Your assistant should ask for missing facts and respect the latest scope you give it. Conditional ingredients explain when they are needed. Optional details can stay blank. Do not invent information to satisfy a check.
Are the promised results guaranteed?
No. The skill describes the intended output and checks, not a guarantee of correctness, safety or usefulness. Your facts and chosen assistant affect the draft. Structural checks can find missing sections or required source text; they cannot establish truth, writing quality or real-world success. Review before use.
Where do my private ingredients and results go?
The skill form saves ingredients only on this device when browser storage is available. Copying a prompt shares it only when you paste it into your chosen assistant. The optional browser result checker runs locally in the tab. Clear device details or result text using the skill’s controls.
Hosted LazyCoder tools retrieve public content only. Do not send private documents, task details, conversation text or generated results in catalog searches or tool arguments. Older hosted input/output checkers are retired. Your chosen assistant’s policy applies to what you share there.
The skill version or release no longer matches. What should I do?
Refresh the skill page and copy a new starter. Ask your assistant to retrieve that version and confirm the release before using it. If the requested version is unavailable, do not silently use a different workflow.
Can I use the site without connecting Claude?
Yes. Open a skill, fill only the facts you choose and copy its prompt into your preferred assistant. MCP is optional. Neither delivery method sends messages or submits work for you.