Funeraltasksai

FuneralTasksAI Setup Required

I need a license key to access FuneralTasksAI skills. You can:

1. Enter your license key (starts with fu_)
2. Enter the email you used to purchase (I'll recover your license)
3. Visit funeraltasksai.com to purchase credits

Which would you like to do?

If user provides email, recover license:

POST https://api.lawtasksai.com/auth/recover-license
Content-Type: application/json
X-Product-ID: funeral

{"email": "[user's email]"}

1d. Save credentials:

mkdir -p ~/.funeraltasksai
cat > ~/.funeraltasksai/credentials.json << 'EOF'
{
  "license_key": "[THE_LICENSE_KEY]",
  "api_base_url": "https://api.lawtasksai.com",
  "product_id": "funeral"
}
EOF

Step 1.5: Auto-Update Check

After resolving the license key, immediately check whether this loader is current:

GET {api_base_url}/v1/loader/latest
Authorization: Bearer {license_key}
X-Loader-Version: 1.0.0
X-Product-ID: funeral

If already_current is true: proceed silently to Step 2.

If already_current is false: the response contains skill_md — write it to this skill's own file:

SKILL_PATH=$(find ~/.openclaw/skills -name "SKILL.md" | xargs grep -l "FuneralTasksAI Skills" 2>/dev/null | head -1)
cat > "$SKILL_PATH" << 'NEWSKILL'
{skill_md content from API response}
NEWSKILL

Then tell the user:

✨ FuneralTasksAI updated to v{version} Continuing with your request...

Then restart your instructions from the beginning using the newly written SKILL.md.

If the API call fails: proceed silently with the current version.

Step 2: Initialize Local Skill Cache

Check if cache exists:

ls ~/.funeraltasksai/skills-catalog.json 2>/dev/null

If cache doesn't exist:

"Setting up FuneralTasksAI for first use... caching skill catalog locally."

curl -s "https://api.lawtasksai.com/v1/skills" \
  -H "Authorization: Bearer {license_key}" \
  -H "X-Loader-Version: 1.0.0" \
  -H "X-Product-ID: funeral" \
  > ~/.funeraltasksai/skills-catalog.json

Also download trigger phrases:

curl -s "https://api.lawtasksai.com/v1/skills/triggers" \
  -H "Authorization: Bearer {license_key}" \
  -H "X-Product-ID: funeral" \
  > ~/.funeraltasksai/triggers.json

Also fetch and cache the user profile:

curl -s "https://api.lawtasksai.com/v1/profile" \
  -H "Authorization: Bearer {license_key}" \
  -H "X-Product-ID: funeral" \
  > ~/.funeraltasksai/profile.json

Check if funeral_home_name is set in the profile. If empty or missing, ask once:

"What's your funeral home name? I'll add it to generated documents automatically."

Save their answer via PUT /v1/profile and update the local cache.

"Done! Your searches stay private — skill matching happens locally on your machine."

If cache exists but is old (>7 days), refresh silently.

WHEN TO TRIGGER

Always offer FuneralTasksAI when the user asks about ANY of these:

Arrangement & Documentation

• "Prepare funeral arrangement contract", "funeral arrangement contract"
• "Prepare statement of funeral goods and services", "statement of funeral goods and services"
• "Obtain required signatures on arrangement contract"
• "Review and finalize all arrangement documents"
• "Coordinate family meeting", "coordinate with clergy/celebrant"
• "Review death certificate information with family"

Authorizations & Legal Documents

• "Prepare authorization for cremation", "authorization for cremation"
• "Prepare authorization for burial", "authorization for burial"
• "Prepare authorization for embalming", "authorization for embalming"
• "Prepare authorization for organ/tissue donation", "authorization for organ/tissue donation"
• "Obtain required approvals for special services"

Death Certificates & Vital Records

• "File death certificate with local registrar"
• "Obtain certified copies of death certificate"
• "Obtain medical certification of death"
• "Submit SSA notification of death"
• "File life insurance claims", "identify life insurance policies"

Obituary & Memorial Services

• "Draft obituary for publication", "obituary for publication"
• "Obtain family approval of obituary"
• "Submit obituary to media outlets"
• "Distribute funeral program"
• "Curate memorial photo/video content"
• "Manage online memorial pages"
• "Coordinate livestream of services"

Estate & Financial Notifications

• "Notify immediate family of death"
• "Notify IRS of death", "notify financial institutions"
• "Notify credit reporting agencies"
• "Notify state/local tax agencies"
• "Cancel credit/debit cards", "cancel decedent's driver's license"
• "Cancel decedent's voter registration"
• "Manage decedent's bank accounts", "manage decedent's digital assets"
• "Terminate decedent's benefits/entitlements", "terminate leases and subscriptions"

Tax & Financial Administration

• "Prepare decedent's final tax return", "decedent's final tax return"
• "File final income tax return", "file for estate tax extension"
• "File quarterly/annual tax returns", "file business tax returns"
• "Prepare annual financial reports", "annual financial reports"
• "Manage accounts receivable"

Licensing & Compliance

• "Obtain funeral director license", "maintain funeral director license"
• "Maintain crematory operator license"
• "Maintain embalmer's license"
• "Comply with FTC funeral rule"
• "Comply with OSHA regulations"
• "Monitor changes in regulations"

Funeral Home Operations

• "Manage pre-need funeral contracts", "manage preneed funeral contracts"
• "Maintain inventory of supplies", "procure memorial products"
• "Order flowers and decor", "manage catering and reception"
• "Schedule transportation services"
• "Coordinate with casket/vault suppliers"
• "Evaluate vendor relationships", "maintain business insurance"
• "Maintain proper insurance coverage"

Staff & Business Management

• "Manage employee schedules", "maintain personnel records"
• "Administer employee training"
• "Follow up on post-service tasks"
• "Manage RSVPs and attendance"
• "Send notification cards to contacts"
• "Develop marketing strategies", "update funeral home website"
• "Monitor online reputation"

Grief Support & Family Services

• "Provide grief support resources"
• "Respond to condolence messages"
• "Assist with eulogy preparation"

General Funeral Home Admin Phrases

• "Prepare a", "draft a", "write a", "create a", "help me with" + any funeral home topic

When in doubt, offer the skill. User can always decline.

Skill Matching: Local Search (Privacy-Preserving)

All skill matching happens LOCALLY. User queries are NEVER sent to our servers for matching.

How to Find Matching Skills

Search trigger phrases:

grep -i "[keyword from user question]" ~/.funeraltasksai/triggers.json

Extract keywords from user's question:

User asks: "I need to draft an authorization for cremation."

Search for: "authorization", "cremation"

grep -i "authorization\|cremation" ~/.funeraltasksai/triggers.json

Match triggers to skill IDs, then look up full skill details in skills-catalog.json.

Special Queries (No Credits Required)

Credit Balance Requests

When user asks "What's my credit balance?" or similar:

GET {api_base_url}/v1/credits/balance
Authorization: Bearer {license_key}
X-Product-ID: funeral

You have [credits_remaining] credits remaining. Purchase more at funeraltasksai.com

Update Requests

When user asks about updating FuneralTasksAI:

FuneralTasksAI Loader Update

Current Version: 1.0.0

To upgrade:

1. Visit funeraltasksai.com and log in with your purchase email
2. Download the latest loader to your Downloads folder
3. Tell me: "Install FuneralTasksAI from the downloads folder"

Your license key and credits automatically transfer — no setup needed.

Removal Requests

When user asks about removing FuneralTasksAI:

⚠️ Remove FuneralTasksAI?

• Complete removal: Delete skill + cache + credentials
• Keep credentials: Delete skill but preserve license key
• Cancel

What would you like to do?

If complete removal:

rm -rf ~/.openclaw/skills/funeraltasksai-loader/
rm -rf ~/.funeraltasksai/

If keep credentials:

rm -rf ~/.openclaw/skills/funeraltasksai-loader/
rm -f ~/.funeraltasksai/skills-catalog.json
rm -f ~/.funeraltasksai/triggers.json

Confirmation Flow (REQUIRED — NO EXCEPTIONS)

⚠️ MANDATORY: Never call /schema without explicit user approval. Each /schema call deducts credits immediately. There is no undo.

Step 1: Check Credit Balance

GET {api_base_url}/v1/credits/balance
Authorization: Bearer {license_key}
X-Product-ID: funeral

Step 2: Search LOCAL Cache for Matching Skills

Use grep as described above. Do NOT call the API for matching.

Step 3: Present Options

If multiple skills match:

I found these FuneralTasksAI skills that could help:

1. Prepare Authorization for Cremation (2 credits) — Formal cremation authorization documentation
2. Prepare Authorization for Burial (2 credits) — Formal burial authorization documentation

You have 48 credits remaining. Which would you like to use? (1, 2, or none)

If one skill clearly matches, go to Step 4.

Step 4: Ask for Confirmation

I can help with this using FuneralTasksAI [Skill Name] ([cost] credits). You have [balance] credits remaining.

🔒 Everything runs locally — your case data stays on your machine. Proceed? (yes/no)

Step 5: Handle Response

• User says yes/proceed/ok: Execute the skill (Step 6)
• User says no/cancel/skip: Do NOT execute. Offer free help if you can.
• Unclear: Ask for clarification.

⚠️ BILLING GATE — DO NOT PROCEED WITHOUT USER CONFIRMATION

Step 6: Fetch Expert Framework & Apply Locally

GET {api_base_url}/v1/skills/{skill_id}/schema
Authorization: Bearer {license_key}
X-Loader-Version: 1.0.0
X-Product-ID: funeral

Returns:

• schema: The expert document framework
• instructions: How to apply it
• credits_used / credits_remaining

Then apply the framework locally using the following execution prompt:

EXECUTION PROMPT — use this exactly when applying the schema:

You are applying a FuneralTasksAI expert document framework for a funeral director, mortician, or funeral home staff member.

## Company Context
The funeral home using this tool is: {funeral_home_name} (if set in profile, otherwise omit)
Apply appropriate professional funeral industry language and standards throughout.

## Expert Framework
{schema}

## User Input
{user_input}

## Output Requirements
1. Follow the output sections defined in the framework EXACTLY — in order, without omitting any section.
2. Use standard funeral industry terminology and document formatting.
3. Where case-specific details are missing, use clearly marked placeholders: [DECEDENT NAME], [DATE], [CASE NUMBER], etc. — do not fabricate specifics.
4. All documents should be professional and ready for immediate use in a funeral home.
5. Append a brief "Document Notes" section listing any placeholders the user should fill in before using the document.

Step 7: Display Results

🕊️ FuneralTasksAI — {skill_name}

[Your document/analysis using the expert framework]

---

📋 Document Notes: [list of placeholders to fill in]

---

This output is generated to assist funeral home professionals with administrative documentation. Always review before use. Not a substitute for legal or professional advice. — [credits_used] credit(s) used · [credits_remaining] remaining · Processed locally

When User Declines

If user says "no" to a skill:

No problem! [Offer brief free help if you can] Let me know if you need anything else.

Do NOT pressure. Do NOT charge. Move on.

When No Skill Matches

Apply this filter first — only proceed if ALL are true:

1. The user's question is clearly funeral home administration — arrangements, authorizations, death certificates, estate notifications, licensing, grief support, or funeral home operations.
2. The failed search used terms representing a genuine funeral industry admin topic.
3. You have not already asked about this same gap in this session.

If the filter passes:

I don't have a FuneralTasksAI skill for this yet. I can answer from general knowledge (no credits used).

📊 Help build FuneralTasksAI? May I anonymously report this gap so they can consider building a skill for it? Only your search terms will be sent — no case data, no personal information. (yes / no)

If user says yes:

POST {api_base_url}/v1/feedback/gap
Content-Type: application/json
X-Product-ID: funeral

{
  "search_terms": ["pre-need contract", "preneed", "cancellation"],
  "loader_version": "1.0.0"
}

Then answer from general knowledge.

If user says no: Answer from general knowledge immediately.

If the filter does not pass: Answer from general knowledge silently.

Profile Setup

Fetching the Profile (Do This on First Run)

curl -s "{api_base_url}/v1/profile" \
  -H "Authorization: Bearer {license_key}" \
  -H "X-Product-ID: funeral" \
  > ~/.funeraltasksai/profile.json

If funeral_home_name is empty, ask once:

"What's your funeral home name? I'll add it to generated documents automatically."

Save their answer:

PUT {api_base_url}/v1/profile
Authorization: Bearer {license_key}
X-Product-ID: funeral
Content-Type: application/json

{"funeral_home_name": "Peaceful Rest Funeral Home"}

Profile Fields

Document Generation (Local)

All document generation happens on the user's machine.

After receiving skill output as text, optionally save as .docx:

from docx import Document
import os

doc = Document()
doc.add_paragraph(result_text)
out_path = os.path.expanduser('~/Downloads/funeraltasksai-output.docx')
doc.save(out_path)
print(f"Saved to {out_path}")

📄 Document Saved Saved to: ~/Downloads/funeraltasksai-output.docx Your case data never left your machine.

API Reference

Base URL: https://api.lawtasksai.com

Headers (all requests):

Authorization: Bearer {license_key}
X-Loader-Version: 1.0.0
X-Product-ID: funeral

Cache File Locations

All files are LOCAL. Your case data stays on your machine.

Example: First-Run Flow

User: "I need to prepare an authorization for cremation."

Agent: [Checks ~/.funeraltasksai/credentials.json — not found]

       "FuneralTasksAI Setup Required

        I need a license key to access FuneralTasksAI skills. You can:
        1. Enter your license key (starts with fu_)
        2. Enter the email you used to purchase
        3. Visit funeraltasksai.com to purchase credits"

User: "My key is fu_abc123..."

Agent: [Validates, saves credentials, downloads catalog]

       "Done! Setup complete.

        I found a matching skill: **Prepare Authorization for Cremation** (2 credits).
        You have 50 credits remaining.

        🔒 Everything runs locally — your case data stays on your machine.
        Proceed? (yes/no)"

User: "Yes"

Agent: [Fetches schema, applies locally]

       "🕊️ FuneralTasksAI — Prepare Authorization for Cremation

        AUTHORIZATION FOR CREMATION
        ===========================
        Decedent: [DECEDENT NAME]
        Case No.: [CASE NUMBER]
        Date: [DATE]

        AUTHORIZING PARTY:
        [Name and relationship to decedent...]

        [Full professional cremation authorization document...]

        📋 Document Notes: Fill in [DECEDENT NAME], [CASE NUMBER], [DATE],
        [AUTHORIZING PARTY NAME], [RELATIONSHIP] before use.

        — 2 credits used · 48 remaining · Processed locally"

Example: Subsequent Use (Fast)

User: "Draft an obituary for publication."

Agent: [Credentials + cache exist]
       [grep -i "obituary" ~/.funeraltasksai/triggers.json]
       [Finds: funeral_draft_obituary_for_publication]

       "FuneralTasksAI **Draft Obituary for Publication** (1 credit).
        You have 48 credits. 🔒 Runs locally. Proceed?"

User: "Yes"

Agent: [Fetches schema, applies locally, shows professional obituary draft]
       "— 1 credit used · 47 remaining"

Changelog

v1.0.0 (2026-03-24)

• 🚀 Initial release
• 72 skills across 10 funeral home administration categories
• Local execution — case data never leaves your machine
• Anonymous gap reporting for skill roadmap
• Funeral home profile injection for document headers