Research Ops

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.

affaan-m/ecc·7.7Kinstalls273.3Kstars

SKILL.md

Full skill instructions

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

Install skill

Copy and run in your terminal

npx -y skills add https://github.com/affaan-m/ecc --skill research-ops

View on GitHub

research-ops

security-review
Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.
17.3K installs
golang-patterns
Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.
14.8K installs
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
14.2K installs
frontend-patterns
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.
14.1K installs

More skills from affaan-m

affaan-m/ecc

coding-standards

Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.

273.3K 14K

View

affaan-m/ecc

golang-testing

Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.

273.3K 13.1K

View

affaan-m/ecc

docker-patterns

Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration.

273.3K 12.7K

View

affaan-m/ecc

springboot-patterns

Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.

273.3K 12.2K

View

affaan-m/ecc

video-editing

AI-assisted video editing workflows for cutting, structuring, and augmenting real footage. Covers the full pipeline from raw capture through FFmpeg, Remotion, ElevenLabs, fal.ai, and final polish in Descript or CapCut. Use when the user wants to edit video, cut footage, create vlogs, or build video content.

273.3K 12.2K

View

affaan-m/ecc

python-patterns

Pythonic idioms, PEP 8 standards, type hints, and best practices for building robust, efficient, and maintainable Python applications.

273.3K 12.1K

View

affaan-m/ecc

frontend-slides

Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.

273.3K 12.1K

View

affaan-m/ecc

api-design

REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.

273.3K 11.9K

View

affaan-m/ecc

django-patterns

Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.

273.3K 11.9K

View

affaan-m/ecc

postgres-patterns

PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices.

273.3K 11.9K

View

affaan-m/ecc

tdd-workflow

Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

273.3K 11.6K

View

affaan-m/ecc

prompt-optimizer

Analyze raw prompts, identify intent and gaps, match ECC components (skills/commands/agents/hooks), and output a ready-to-paste optimized prompt. Advisory role only — never executes the task itself. TRIGGER when: user says "optimize prompt", "improve my prompt", "how to write a prompt for", "help me prompt", "rewrite this prompt", or explicitly asks to enhance prompt quality. Also triggers on Chinese equivalents: "优化prompt", "改进prompt", "怎么写prompt", "帮我优化这个指令". DO NOT TRIGGER when: user wants the task executed directly, or says "just do it" / "直接做". DO NOT TRIGGER when user says "优化代码", "优化性能", "optimize performance", "optimize this code" — those are refactoring/performance tasks, not prompt optimization.

273.3K 11.3K

View