AGENT SKILL

research-ops

Evidence-first current-state research workflow for ECC. Use when the user wants fresh facts, comparisons, enrichment, or a recommendation built from current public evidence and any supplied local context.

License 许可
MIT
所属仓库
agisota/old-one
最近更新
2026-07-04
Stars
★ 3
Forks
1

01 前言 Front Matter

name
research-ops
origin
ECC
description
Evidence-first current-state research workflow for ECC. Use when the user wants fresh facts, comparisons, enrichment, or a recommendation built from current public evidence and any supplied local context.

03 SKILL.md 正文

Research Ops

Use this when the user asks to research something current, compare options, enrich people or companies, or turn repeated lookups into a monitored workflow.

This is the operator wrapper around the repo's research stack. It is not a replacement for deep-research, exa-search, or market-research; it tells you when and how to use them together.

Skill Stack

Pull these ECC-native skills into the workflow when relevant:

  • exa-search for fast current-web discovery
  • deep-research for multi-source synthesis with citations
  • market-research when the end result should be a recommendation or ranked decision
  • lead-intelligence when the task is people/company targeting instead of generic research
  • knowledge-ops when the result should be stored in durable context afterward

When to Use

  • user says "research", "look up", "compare", "who should I talk to", or "what's the latest"
  • the answer depends on current public information
  • the user already supplied evidence and wants it factored into a fresh recommendation
  • the task may be recurring enough that it should become a monitor instead of a one-off lookup

Guardrails

  • do not answer current questions from stale memory when fresh search is cheap
  • separate:
    • sourced fact
    • user-provided evidence
    • inference
    • recommendation
  • do not spin up a heavyweight research pass if the answer is already in local code or docs

Workflow

1. Start from what the user already gave you

Normalize any supplied material into:

  • already-evidenced facts
  • needs verification
  • open questions

Do not restart the analysis from zero if the user already built part of the model.

2. Classify the ask

Choose the right lane before searching:

  • quick factual answer
  • comparison or decision memo
  • lead/enrichment pass
  • recurring monitoring candidate

3. Take the lightest useful evidence path first

  • use exa-search for fast discovery
  • escalate to deep-research when synthesis or multiple sources matter
  • use market-research when the outcome should end in a recommendation
  • hand off to lead-intelligence when the real ask is target ranking or warm-path discovery

4. Report with explicit evidence boundaries

For important claims, say whether they are:

  • sourced facts
  • user-supplied context
  • inference
  • recommendation

Freshness-sensitive answers should include concrete dates.

5. Decide whether the task should stay manual

If the user is likely to ask the same research question repeatedly, say so explicitly and recommend a monitoring or workflow layer instead of repeating the same manual search forever.

Output Format

QUESTION TYPE
- factual / comparison / enrichment / monitoring

EVIDENCE
- sourced facts
- user-provided context

INFERENCE
- what follows from the evidence

RECOMMENDATION
- answer or next move
- whether this should become a monitor

Pitfalls

  • do not mix inference into sourced facts without labeling it
  • do not ignore user-provided evidence
  • do not use a heavy research lane for a question local repo context can answer
  • do not give freshness-sensitive answers without dates

Verification

  • important claims are labeled by evidence type
  • freshness-sensitive outputs include dates
  • the final recommendation matches the actual research mode used

04 同仓库更多 Skills

agisota
agisota/old-one

zoom-out

Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.

★ 3
agisota
agisota/old-one

zeroize-audit

Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.

★ 3
agisota
agisota/old-one

yeet

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

★ 3
agisota
agisota/old-one

yara-rule-authoring

Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.

★ 3
agisota
agisota/old-one

x-twitter-growth

X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.

★ 3
agisota
agisota/old-one

x-api

X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.

★ 3