FreeLattice Skill Builder

Drafts FreeLattice form fields and, when the runtime supports artifacts, packages the resulting skill as a zip for import-style workflows.

Security Scan

The skill is an instruction-only template for drafting FreeLattice skill form fields and (optionally) producing a minimal zip; its requirements and instructions are consistent with that purpose and it does not request extra credentials or installs.

Purpose & Capability

The name/description (build FreeLattice form fields and an import-style package) match the SKILL.md. There are no unrelated env vars, binaries, or installs requested. The scope is limited to visible FreeLattice fields and packaging, which is coherent with the stated purpose.

Instruction Scope

The instructions are narrowly focused on producing form fields and a minimal package. They explicitly forbid creating repos, auth flows, or hidden metadata. One point to note: the guidance 'Infer missing details and keep moving' gives the agent latitude to fabricate reasonable defaults when the user omits specifics — this is intentional for usability but could produce invented values if the user expects strict fidelity. The SKILL.md does not instruct reading unrelated files, env vars, or external endpoints.

Install Mechanism

No install spec or code files are present; this is instruction-only so nothing is written to disk by the skill itself unless the runtime supports artifact creation, which is a runtime capability rather than an installed component here.

Credentials

The skill does not request credentials, config paths, or environment variables. The requested capabilities are proportionate to drafting fields and packaging files.

Persistence & Privilege

always is false and the skill does not request persistent or cross-skill configuration or elevated privileges. It may create files only when the runtime allows file creation; that behavior is described in the SKILL.md and is consistent with the stated packaging feature.

Assessment

This skill is an instruction-only template and is internally consistent with its description. Before installing or using it, consider: 1) Provide clear constraints or a stricter schema if you do not want the agent to infer/make up missing values. 2) If your runtime supports file creation, the skill will create a folder, skill.json, README.md, and a zip—verify the generated files before importing them into any environment. 3) Do not include secrets or sensitive account details in the prompt or input fields (the system prompt and input_template will be stored in the generated files). 4) If you prefer the agent not to run autonomously, restrict its invocation in your agent settings; autonomous invocation here is allowed by default but not required. Overall risk is low, but always review generated prompts and package contents before use.

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:

{
  "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"