autosnippet-recipe-candidates

Drafting candidate recipes for a knowledge base without editing final content directly requires a draft-folder workflow outside the final recipes directory. You create one Markdown file per usage pattern, then submit it via MCP for structured review and integration.

The MCP submission process for AutoSnippet recipe drafts involves calling autosnippet_submit_draft_recipes with your draft file paths and targetName. Setting deleteAfterSubmit to true removes the local draft files after publishing them to the dashboard for review.

Yes, you can use a single-pattern file workflow to generate knowledge base recipes. This approach creates one Markdown file per usage pattern in a designated draft folder, ensuring clean separation from final recipes before MCP submission.

Drafting recipe candidates requires a consistent Markdown template that enforces frontmatter and usage sections. This structured format streamlines the review and approval process when submitting drafts to the MCP dashboard.

Using a draft folder outside the recipes directory for candidate recipes prevents direct edits to final content. This separation enforces a formal review process, ensuring only approved recipes integrate into the main knowledge base.

The draft-folder workflow for recipe candidates is limited to single-pattern file workflows and MCP-based submission. It does not support direct edits to final content, requiring all changes to go through the structured dashboard review process.