affaan-m/ecc

research-ops

Evidence-first current-state research workflow for ECC.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/affaan-m/ecc --skill research-ops

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

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

text
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

Related by task

from this repository

More skills

All skills
affaan-m
Community

rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology. Use when writing Rust tests — unit, integration, async, property-based, or coverage.

24h installs
489
GitHub stars
308.2K
Updated
Nov 20
affaan-m
Community

search-first

Research-before-coding workflow: search npm/PyPI, MCP servers, skills, and GitHub for existing tools before writing custom code, then adopt, extend, or build. Launches the researcher agent for non-trivial needs. Use when starting a feature, adding a dependency or integration, or about to write a utility that may already exist.

1h installs
5
GitHub stars
308.2K
Updated
Nov 20
affaan-m
Community

browser-qa

Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.

1h installs
2
GitHub stars
307.9K
Updated
Nov 20
affaan-m
Community

docker-patterns

Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation.

1h installs
2
GitHub stars
307.9K
Updated
Nov 20