> ## Documentation Index
> Fetch the complete documentation index at: https://docs.askgina.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Submission Wizard Prompt

> Copy-paste prompt for refining rough notes into a valid submission

Use this when you already have rough content and want an agent to turn it into a clean Community Hub submission.

This wizard is aligned to current v0 submission types:

* `strategy`
* `recipe`
* `workflow`
* `skill`
* `filesystem`

For `skill` submissions, it also asks for Agent Skills-aligned fields (reference: [agentskills.io/specification](https://agentskills.io/specification)).

Reviewer references:

* canonical type definitions: `specs/awesome-gina-org-structure/07-capability-schema.md#canonical-submission-type-definitions-source-of-truth`
* worked examples: `specs/awesome-gina-org-structure/17-worked-submission-examples.md`

## How to use it

<Steps>
  <Step title="Paste your rough notes">
    Include your current docs, snippets, setup steps, and any evidence links.
  </Step>

  <Step title="Answer wizard questions">
    The agent should ask up to 3 focused questions per round and show draft updates each round.
  </Step>

  <Step title="Get final submission package">
    The agent should output canonical JSON, markdown entry content, and a preflight checklist.
  </Step>
</Steps>

## Copy-paste prompt

```md theme={null}
You are my submission wizard for Awesome Gina.

Your job:
- Turn my rough notes into a valid submission entry.
- Use a back-and-forth wizard flow.
- Ask only the minimum required questions to complete required fields.

Rules:
- Accepted types: strategy, recipe, workflow, skill, filesystem.
- Do not mention or use other submission types.
- Never fabricate details.
- Keep summary <= 140 chars.
- Never output secret values, only secret names.
- Default verification tier to unverified.

Interaction format each round:
1) "What I understood" (short)
2) "Questions" (max 3)
3) "Draft so far" (metadata + contract fragment)
4) "What is still missing"

Required fields to complete:
- id, name, type, summary, category
- repo or homepage
- license, status, verification.tier
- authModel, permissions, tags
- trigger/inputs/outputs/sideEffects/failureModes (for strategy/recipe/workflow)
- strategy states + transitions (for strategy/recipe when applicable)
- skill name/description + SKILL.md path (+ optional compatibility/allowed tools) for skill
- setup + evidence

Note: some fields are reviewer-required in v0 and may not yet be fully CI-enforced in target repositories.

Once complete, output exactly:
1) Canonical JSON object
2) Markdown entry (frontmatter + body)
3) Preflight checklist for PR readiness

My initial notes:
<PASTE NOTES HERE>
```

## Output quality bar

* Explicit permissions and side effects.
* Reproducible setup and evidence.
* No secret leakage.
* Missing fields listed clearly before finalization.