aqe-research
Skill515 starsChanged 22 days agoMITView on GitHub
Conduct evidence-first technical research for Agentic QE, Ruflo, related ruvnet projects, or external tools. Use when Codex must investigate a repository, compare current upstream changes, trace dependencies and history, distinguish verified facts from inference, or synthesize findings into actionable engineering recommendations. Do not use for a simple known-answer lookup or an implementation-only task.
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Read AGENTS.md, the question, and any user-supplied artifacts completely.
- Very specific: line 10
Search local evidence broad-to-narrow with rg --files, rg, code navigation, tests, configuration, documentation, and git history.
- Distinctive: line 29
Use parallel agents only when the user requests delegation or repository instructions explicitly permit it.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Research AQE Systems
- Read
AGENTS.md, the question, and any user-supplied artifacts completely. - Define the decision the research must support, its scope, and freshness needs.
- Search local evidence broad-to-narrow with
rg --files,rg, code navigation, tests, configuration, documentation, and git history. - For current external claims, inspect primary sources: upstream repositories, releases, commits, issues, pull requests, and official documentation. Record dates, versions, commit identifiers, and links.
- Trace definitions to usages and public boundaries. Map dependencies, data flow, CLI/MCP parity, configuration generation, and tests when relevant.
- Classify each material statement using references/evidence-rules.md. Never repeat a benchmark, capability, or roadmap claim as fact without direct evidence.
- Synthesize only after gathering evidence. State contradictions, uncertainty, missing access, and stale documentation explicitly.
- Return:
- the decision-oriented summary;
- verified findings with source locations;
- inferences and their supporting evidence;
- gaps and risks;
- prioritized recommendations and the smallest useful next validation.
Use parallel agents only when the user requests delegation or repository instructions explicitly permit it. Treat Claude agent definitions as domain references; do not copy or execute their Claude-only hooks or tool syntax.
In this repository129 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/commands/monitoring/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- aqe-plan-qualitySkill
- aqe-plan-workSkill
- aqe-review-qualitySkill
- aqe-rufloSkill
- aqe-test-changeSkill
- rufloSkill
- a11y-allySkill
- accessibility-testingSkill
- AgentDB Advanced FeaturesSkill
- AgentDB Learning PluginsSkill
- AgentDB Memory PatternsSkill
- AgentDB Performance OptimizationSkill
- AgentDB Vector SearchSkill
- agentic-quality-engineeringSkill
- api-testing-patternsSkill
- browserSkill
- brutal-honesty-reviewSkill
- bug-reporting-excellenceSkill
- chaos-engineering-resilienceSkill
- cicd-pipeline-qe-orchestratorSkill
- code-review-qualitySkill
- compatibility-testingSkill
- compliance-testingSkill
- consultancy-practicesSkill
- context-driven-testingSkill
- contract-testingSkill
- coverage-drop-investigatorSkill
- coverage-guardSkill
- database-testingSkill
- debug-loopSkill
- e2e-flow-verifierSkill
- enterprise-integration-testingSkill
- exploratory-testing-advancedSkill
- flow-nexus-neuralSkill
- flow-nexus-platformSkill
- flow-nexus-swarmSkill
- freeze-testsSkill
- github-code-reviewSkill
- github-multi-repoSkill
- github-project-managementSkill
- github-release-managementSkill
- github-workflow-automationSkill
- holistic-testing-pactSkill
- Hooks AutomationSkill
- iterative-loopSkill
- localization-testingSkill
- middleware-testing-patternsSkill
- mobile-testingSkill
- mutation-testingSkill
- n8n-expression-testingSkill
- n8n-integration-testing-patternsSkill
- n8n-security-testingSkill
- n8n-trigger-testing-strategiesSkill
- n8n-workflow-testing-fundamentalsSkill
- no-skipSkill
- observability-testing-patternsSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

