Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

research-query

Sterne1

Forks0

Aktualisiert24. April 2026 um 19:42

Searches across existing research briefs for claims, sources, or contradictions matching a query. Read-only — returns matching claims with cites, does not regenerate or re-fetch. Use to check whether a topic has already been researched, to pull specific facts from a prior brief, or to cross-reference claims across multiple briefs. Auto-triggers on: "/research-query", "do we have research on X", "what did the brief on Y say about Z", "find claims about", "search the briefs for", "have we already looked into". Do not use to run new research — use /deep-research for that.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

enchanter-ai

enchanter-ai/wixie

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Kundendienst-MitarbeiterBüro- und Verwaltungsberufe·SOC 43-4051

SKILL.md

readonly

name	research-query
description	Searches across existing research briefs for claims, sources, or contradictions matching a query. Read-only — returns matching claims with cites, does not regenerate or re-fetch. Use to check whether a topic has already been researched, to pull specific facts from a prior brief, or to cross-reference claims across multiple briefs. Auto-triggers on: "/research-query", "do we have research on X", "what did the brief on Y say about Z", "find claims about", "search the briefs for", "have we already looked into". Do not use to run new research — use /deep-research for that.
allowed-tools	Read, Grep, Glob

Research Query

Search existing briefs without regenerating.

Inputs

<query> — free-text question or keyword
Optional: --slug <slug> — limit to one brief
Optional: --min-confidence high|medium|low — filter by confidence tier

Execution

Step 1: Scope

If --slug given → read only state/briefs/<slug>/claims.json. Else → glob state/briefs/*/claims.json.

Step 2: Match

For each brief, scan claims. Match <query> against:

claim text — direct substring and semantic overlap
sub_question label (via trace.json if available)
Source URLs in supporting

Rank matches: direct claim-text > source URL > sub-question.

Step 3: Return

Group by brief slug. For each match:

[<slug>] (freshness: <date>, verdict: <X>)
  C<id>: <claim text> [S1, S3] (confidence: <tier>)
    sources: <url>, <url>

If no matches → no matching claims across <N> briefs searched.

Cap total output at 600 words; if over, return the top 10 matches and append (<K> more matches hidden — run with --slug to narrow).

Rules

Do NOT fetch new sources.
Do NOT re-verify.
Do NOT modify any brief.
Stale briefs (freshness > 30 days) are still returned but tagged (stale) — caller decides whether to re-run /deep-research.
If a brief's verdict is FAIL, tag (unverified) and do not surface its claims as authoritative.

Failure modes

Code	Signature	Counter
F02	Returned a "match" that isn't in any claims.json	Every returned line cites a real claim id from a real brief
F13	Returned adjacent-but-irrelevant claims	Rank by direct match; drop below a relevance floor

Mehr aus diesem Repository

gleiches Repository

deep-research

enchanter-ai/wixie

Deep research engine (E0) that produces a verified, cited claims artifact before prompts are engineered. Decomposes the query, fans out parallel Haiku fetchers, triangulates claims across independent sources, synthesizes, and verifies every claim traces to a fetched quote. Auto-fires inside /create when the topic depends on external or time-sensitive facts. Also callable standalone. Auto-triggers on: "/deep-research", "/research", "research this topic", "look up the current state of", "what's the latest on", "fact-check this", "find sources on", "before we craft the prompt, research". Do not use for static topics (pure logic, timeless writing tasks) or when a fresh brief already exists (freshness < 30 days) — reuse it. Do not use to render an existing brief — use /research-render for that.

2026-05-311

freshness-check

enchanter-ai/wixie

Runs the Wixie model-freshness aggregator over state/model-usage.ndjson and flags any models-registry.json entry whose sunset_date has elapsed. Use when the developer asks about model deprecation, registry staleness, retired models, sunset dates, F-006 closure, or wants a current freshness summary. Auto-triggers on: "model freshness", "registry stale", "deprecated models", "sunset", "F-006", "freshness report", "model usage telemetry". Do not use for emitting telemetry events (the SessionStart hook does that automatically) or for editing the registry itself (developer edits the JSON directly).

2026-05-061

converge

enchanter-ai/wixie

Run the Convergence Engine on any prompt file. Iterates up to 100 times, automatically fixing clarity, completeness, efficiency, model fit, and failure resilience until the prompt reaches DEPLOY quality. Auto-triggers on: "/converge", "converge this prompt", "optimize until perfect", "iterate until deploy", "run convergence".

2026-05-051

prompt-creator

enchanter-ai/wixie

Creates optimized, model-fitted prompts from raw task descriptions with technique selection and explained reasoning. Auto-triggers on: "I need a prompt for", "build me a prompt", "make this prompt better", "optimize this prompt", "help me prompt", "write a system prompt", "what prompting technique should I use", "how should I structure this prompt", "/create".

2026-05-051

harden

enchanter-ai/wixie

Tests a prompt for security vulnerabilities — injection attacks, jailbreak patterns, data leakage risks. Reports exploits found and suggests specific defenses. Use on any user-facing or API-deployed prompt. Auto-triggers on: "/harden", "harden this prompt", "test for injection", "is this prompt safe", "security check prompt", "red team this prompt".

2026-05-051

prompt-improver

enchanter-ai/wixie

Improves existing prompts by re-selecting techniques, adapting format to the target model, and fixing weaknesses while preserving the user's intent and domain knowledge. Auto-triggers on: "make this prompt better", "improve this prompt", "refine this prompt", "fix this prompt", "optimize this prompt", "what's wrong with this prompt", "/refine".

2026-05-051

name	research-query
description	Searches across existing research briefs for claims, sources, or contradictions matching a query. Read-only — returns matching claims with cites, does not regenerate or re-fetch. Use to check whether a topic has already been researched, to pull specific facts from a prior brief, or to cross-reference claims across multiple briefs. Auto-triggers on: "/research-query", "do we have research on X", "what did the brief on Y say about Z", "find claims about", "search the briefs for", "have we already looked into". Do not use to run new research — use /deep-research for that.
allowed-tools	Read, Grep, Glob

Research Query

Search existing briefs without regenerating.

Inputs

<query> — free-text question or keyword
Optional: --slug <slug> — limit to one brief
Optional: --min-confidence high|medium|low — filter by confidence tier

Execution

Step 1: Scope

If --slug given → read only state/briefs/<slug>/claims.json. Else → glob state/briefs/*/claims.json.

Step 2: Match

For each brief, scan claims. Match <query> against:

claim text — direct substring and semantic overlap
sub_question label (via trace.json if available)
Source URLs in supporting

Rank matches: direct claim-text > source URL > sub-question.

Step 3: Return

Group by brief slug. For each match:

[<slug>] (freshness: <date>, verdict: <X>)
  C<id>: <claim text> [S1, S3] (confidence: <tier>)
    sources: <url>, <url>

If no matches → no matching claims across <N> briefs searched.

Cap total output at 600 words; if over, return the top 10 matches and append (<K> more matches hidden — run with --slug to narrow).

Rules

Do NOT fetch new sources.
Do NOT re-verify.
Do NOT modify any brief.
Stale briefs (freshness > 30 days) are still returned but tagged (stale) — caller decides whether to re-run /deep-research.
If a brief's verdict is FAIL, tag (unverified) and do not surface its claims as authoritative.

Failure modes

Code	Signature	Counter
F02	Returned a "match" that isn't in any claims.json	Every returned line cites a real claim id from a real brief
F13	Returned adjacent-but-irrelevant claims	Rank by direct match; drop below a relevance floor