query-asset-candidates

name	query-asset-candidates
description	Use when searching generated asset candidates, scores, metadata, lineage, prompt history, or previous rejects before generating more assets.
version	1.0.0
author	Project Agents
license	Project-internal
metadata	{"hermes":{"tags":["asset-index","search","metadata"],"related_skills":["asset-metadata-writer","asset-gacha-session"]}}

Query Asset Candidates

Overview

Prevents duplicate generation and lets agents learn from prior prompt history.

When to Use

• Before generating a new asset role.
• When checking prior shortlist/rejects.
• When finding high-score prompts for reuse.

Data Source

Default index:

Generatedres://index.jsonl

Query Examples

asset_type: common_enemy
status: shortlisted
style_kit: Bio Goo Nursery
lineage_id: pod_chaser_family
min_taste_score: 20

Output Contract

matches:
  - candidate_id:
    asset_id:
    preview:
    metadata_path:
    status:
    scores:
    why_kept_or_rejected:

Common Pitfalls

1. Generating new candidates without checking existing ones.
2. Ignoring rejected prompts that document failure modes.
3. Losing lineage continuity.

Verification Checklist

• Query criteria stated
• Metadata paths returned
• Prior decisions summarized