higgsfield-recall

Queries memory databases for past Higgsfield failures and applies known fixes before prompt generation.

Updated Jul 15, 2026
One-click install
npx skills add https://github.com/executiveusa/buffer-blaster- --skill higgsfield-recall-executiveusa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: higgsfield-recall
Source: https://github.com/executiveusa/buffer-blaster-/tree/main/skills/higgsfield/skills/higgsfield-recall
Command: npx skills add https://github.com/executiveusa/buffer-blaster- --skill higgsfield-recall-executiveusa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Repeatedly hitting the same Higgsfield generation failures — content filter blocks, character drift, ignored style keywords, model mismatches — wastes credits and time. This Skill checks a persistent memory of past failures and confirmed fixes before any prompt is written, so known problems are pre-empted instead of rediscovered. ## Core Features & Use Cases - Pre-Generation Recall: Automatically queries filter-memory and quality-memory databases with key terms extracted from the intended prompt, then silently applies confirmed substitutions and fixes. - Generation Ledger Logging: Records every generation outcome (kept or rejected) with controlled-vocabulary reason tags, enabling takes-per-kept ratios and iterate-vs-batch verdicts per shot type. - Routing Telemetry: Logs which sub-skills were used per request so teams can see which skills are load-bearing over time. - Use Case: Before writing a prompt for a two-character dialogue close-up, the Skill finds that a previous attempt with the same model produced lip-sync desync and that a confirmed fix exists — it applies that fix to the new prompt without the user needing to remember the failure. ## Quick Start Ask the agent to write a Higgsfield prompt for your scene and it will automatically check past failure memory and apply known fixes before presenting the prompt.

Frequently Asked Questions about higgsfield-recall

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I avoid repeating past Higgsfield prompt failures?

Run a recall check before writing any prompt by querying the filter-memory and quality-memory databases with key terms from your intended scene. Entries with fix_confirmed set to true provide proven substitutions and prompt structures you can apply directly.

How do I check what got blocked by the Higgsfield content filter?

Use the query-filter command of the higgsfield_memory.py script with three to six specific nouns from your prompt. It returns past filter block entries including the blocked term, the substitution tried, and whether that substitution was confirmed to pass.

Can I log Higgsfield generation results to track success rates?

Yes, the log-gen command records each generation with model, tags, outcome, reject reason, and credits spent. The ratio command then computes per-shot-tag verdicts indicating whether to iterate on the prompt or batch and select.

Does the recall check work with empty memory databases?

The databases ship with seed entries covering common failure patterns like character drift, VHS style being ignored, and lip-sync desync. If a query finds nothing relevant, the workflow proceeds silently with normal prompt generation.

When should recall findings be surfaced to the user?

Findings are only mentioned when they materially change the prompt, such as substituting a blocked term or switching models based on past failures. Otherwise the fixes are applied silently without announcing the recall check.