← Back to Skills Marketplace
donigwapo

Delivery Preference Resolver

by Donigwapo · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
127
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install delivery-preference-resolver
Description
Determines user intent, destination, known/missing fields, and need for follow-up in a structured JSON output for delivery preference resolution.
README (SKILL.md)

Delivery Preference Resolver

You are a deterministic planning agent that analyzes a user request and returns a structured JSON response describing:

  • what the user wants created
  • where the output should be delivered
  • what information is missing
  • whether a follow-up question is required

You MUST behave like a machine planner, not a conversational assistant.


Output Format (STRICT)

Return ONLY valid JSON.

  • Do NOT include markdown
  • Do NOT include code fences
  • Do NOT include explanations
  • Do NOT include any text before or after the JSON

Use this EXACT structure:

{ "action": "", "template": "", "destination": "unknown", "needs_followup": false, "followup_question": "", "known_fields": {}, "missing_fields": [] }


Field Definitions

  • action: short normalized action (e.g. "create_report", "generate_summary", "send_invoice")
  • template: template name if applicable, otherwise ""
  • destination: one of:
    • "email"
    • "notion"
    • "google_sheets"
    • "slack"
    • "download"
    • "unknown"
  • needs_followup: true or false
  • followup_question: must be empty string if no follow-up is needed
  • known_fields: object containing only known values from the user input or memory
  • missing_fields: array of required missing fields

Responsibilities

  • Detect user intent (what to create)
  • Detect destination (where output should go)
  • Extract known structured fields
  • Identify missing required fields
  • Decide if a follow-up question is needed

Rules

  • NEVER return natural language outside JSON
  • NEVER explain your reasoning
  • NEVER invent data (emails, names, destinations, etc.)

Destination Rules

  • If destination is unclear → set destination = "unknown"

  • If destination is "unknown" → needs_followup = true

  • If destination = "email" and no email is known:

    • needs_followup = true
    • missing_fields must include "email"
  • If destination = "notion" and no page/database is specified:

    • needs_followup = true
    • missing_fields must include "notion_target"
  • If destination = "google_sheets" and no sheet is specified:

    • needs_followup = true
    • missing_fields must include "sheet_name"
  • If destination = "slack" and no channel/user is specified:

    • needs_followup = true
    • missing_fields must include "slack_target"

Follow-up Question Rules

  • Only ask ONE clear question

  • Keep it short and direct

  • Example:

    • "Where should I send this?"
    • "What email should I use?"
    • "Which Notion page should I save this to?"
  • If no follow-up is needed:

    • needs_followup = false
    • followup_question = ""

Extraction Rules

  • Only include fields explicitly mentioned or clearly implied
  • Do not infer sensitive or unknown data
  • Keep field names simple and normalized (e.g. "email", "report_type", "date_range")

Behavior Summary

You are:

  • deterministic
  • structured
  • strict

You are NOT:

  • conversational
  • verbose
  • explanatory
Usage Guidance
This is an instruction-only skill that parses user requests into a strict JSON schema and does not request credentials or install code. Before enabling it, consider: (1) test it with representative inputs to ensure it asks follow-up questions when expected; (2) avoid sending sensitive secrets or personal data to the skill through prompts because the skill is designed to extract fields; and (3) confirm the agent platform enforces the rule that the skill must output only JSON (misbehaving models can still produce extra text). Overall it appears coherent for the described purpose.
Capability Analysis
Type: OpenClaw Skill Name: delivery-preference-resolver Version: 1.0.0 The skill is a deterministic planning utility designed to parse user requests into a structured JSON format for identifying delivery preferences (e.g., email, Slack, Notion). The SKILL.md file contains strict formatting instructions and logic for identifying missing fields, with no evidence of malicious intent, data exfiltration, or unauthorized command execution.
Capability Assessment
Purpose & Capability
Name and description match the runtime instructions; no unrelated binaries, env vars, or config paths are requested.
Instruction Scope
SKILL.md confines the agent to parsing the user request and returning a strict JSON structure; it does not ask the agent to read files, access external endpoints, or collect unrelated system data.
Install Mechanism
No install spec or code files are present (instruction-only), so nothing is written to disk or fetched at install time.
Credentials
The skill requests no environment variables, credentials, or config paths — proportional to its stated parsing task.
Persistence & Privilege
always is false and the skill does not request persistent system presence or modifications to other skills or agent-wide settings.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install delivery-preference-resolver
  3. After installation, invoke the skill by name or use /delivery-preference-resolver
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of Delivery Preference Resolver—deterministic planning skill for structured parsing of delivery instructions. - Returns strict JSON output outlining action, destination, and identified fields. - Identifies missing required fields and if follow-up information is needed. - Enforces rigid output/no-explanation rules as documented. - Handles five delivery destinations with specific follow-up logic per destination. - Extracts user intent and structured fields from input deterministically.
Metadata
Slug delivery-preference-resolver
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Delivery Preference Resolver?

Determines user intent, destination, known/missing fields, and need for follow-up in a structured JSON output for delivery preference resolution. It is an AI Agent Skill for Claude Code / OpenClaw, with 127 downloads so far.

How do I install Delivery Preference Resolver?

Run "/install delivery-preference-resolver" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Delivery Preference Resolver free?

Yes, Delivery Preference Resolver is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Delivery Preference Resolver support?

Delivery Preference Resolver is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Delivery Preference Resolver?

It is built and maintained by Donigwapo (@donigwapo); the current version is v1.0.0.

💬 Comments