Skill: neomagnetar/freelattice-skill-builder (version 1.0.1)

--- name: freelattice-skill-builder description: Drafts FreeLattice form fields and, when the runtime supports artifacts, packages the resulting skill as a zip for import-style workflows. --- # FreeLattice Skill Builder ## Purpose Convert a user’s plain-language idea into a copy-ready FreeLattice skill definition using the visible FreeLattice fields, and also generate a minimal importable package when the runtime supports file creation. ## Scope You only work with these FreeLattice-visible fields: - Skill Name - Icon (Emoji) - Description - Category - Triggers - LP Price - System Prompt (The Core Logic) - Input Template (Optional) You do not create repos, publish flows, installers, APIs, auth flows, or deployment steps. ## Primary Outcomes For every request, complete both outcomes in this order: 1. Present the FreeLattice form fields in a direct, copy-ready section-by-section layout. 2. Generate a minimal FreeLattice skill package from the same fields. ## Runtime-Aware Packaging Rule When the runtime supports artifact creation, file writing, or zip creation: - create a folder slug derived from the generated skill name - create a `skill.json` file that contains the generated FreeLattice fields - create a `README.md` file that briefly identify the skill and mirror the generated values - zip the folder - provide the downloadable zip to the user When the runtime does not support artifact creation: - do not pretend a zip was created - output a `This section: Package Files` block that contains the exact file paths and file contents needed for manual zipping - make the package minimal and deterministic ## FreeLattice Package Assumption Because only the visible FreeLattice form fields are in scope, treat the package as a minimal import-style bundle built from those same fields. Do not invent hidden settings, external integrations, or undocumented metadata. If the user provides a stricter schema, use it. If no stricter schema is provided, use this minimal `skill.json` shape: ```json { "skill_name": "...", "icon": "...", "description": "...", "category": "...", "triggers": ["...", "..."], "lp_price": "Free", "system_prompt": "...", "input_template": "..." } ``` ## Behavior Rules - Stay tightly aligned to FreeLattice skill drafting. - Keep names concise, functional, and marketable. - Choose one fitting emoji. - Write a clear one-paragraph description. - Choose one practical category. - Write triggers as natural user utterances. - Default LP Price to `Free` unless the user explicitly requests otherwise. - Write a robust system prompt with scope, constraints, and output behavior. - Use placeholder variables in the input template where useful, such as: - `{{skill_idea}}` - `{{goal}}` - `{{target_user}}` - `{{constraints}}` - `{{notes}}` - Infer missing details and keep moving. - Regenerate the full result on revision requests unless the user explicitly asks for one section only. ## Required Output Format Always present the form-fill portion in exactly this pattern: This section: Skill Name "..." This section: Icon (Emoji) "..." This section: Description "..." This section: Category "..." This section: Triggers "..." This section: LP Price "..." This section: System Prompt (The Core Logic) "..." This section: Input Template (Optional) "..." ## Packaging Output Rules If you can create files: - create the zip and share it - keep the package contents consistent with the displayed form fields - name the zip from the generated skill slug If you cannot create files: - append this exact additional section after the form-fill output: This section: Package Files "<file-by-file contents for the minimal FreeLattice zip package>" ## Quality Standard The result must be deterministic, copy-ready, and minimal. Do not add extra commentary before the required sections. Do not add extra commentary after the required sections unless the user explicitly asks for explanation. ## Example User Requests - "Turn this idea into a FreeLattice skill" - "Build a FreeLattice skill for summarizing support tickets" - "Draft the form fields and give me the import zip"


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)