New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Qe Context Driven Testing

by proffesor-for-testing in proffesor-for-testing/agentic-qe

Apply context-driven testing principles where practices are chosen based on project context, not universal 'best practices'.

MITAuto-check passed

Install Qe Context Driven Testing

skills CLI
$ npx skills add proffesor-for-testing/agentic-qe --skill qe-context-driven-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install proffesor-for-testing/agentic-qe qe-context-driven-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.kiro/skills/qe-context-driven-testing .claude/skills/qe-context-driven-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
qe-context-driven-testing
GitHub stars
494
Token cost
~1.7k tokens
SKILL.md length
582 words
Files
1
Skills in repo
111
Repo updated
First seen
Licence
MIT

At a glance

Apply context-driven testing principles where practices are chosen based on project context, not universal 'best practices'.

  • Works in 5 steps: ANALYZE context: project goals,… → QUESTION practices: "Why this? What risk… → INVESTIGATE not just check: Does… → …
  • Making testing decisions
  • SKILL.md covers Quick Reference Card, Context-Driven Decisions, Investigation vs. Checking and Red Flags: Not Context-Driven, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Qe Context Driven Testing is an agent skill from proffesor-for-testing/agentic-qe. Apply context-driven testing principles where practices are chosen based on project context, not universal 'best practices'. Use when making testing decisions, questioning dogma, or adapting approaches to specific project needs.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Agentic QE Fleet is an open-source AI-powered QA/QE platform designed for use with Coding Agents (works best with Claude Code) featuring specialized agents and skills to support… The licence is MIT.

When your agent uses it

  • Making testing decisions
  • Questioning dogma
  • Adapting approaches to specific project needs

Example prompts

  • “best practices”
  • “/qe-context-driven-testing”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. ANALYZE context: project goals, constraints, risks, team skills
  2. QUESTION practices: "Why this? What risk does it address? What's the cost?"
  3. INVESTIGATE not just check: Does software solve the problem, or create new ones?
  4. ADAPT approach based on context, not "best practices"
  5. DOCUMENT discoveries, not pre-written plans

What it can do on your machine

Read from SKILL.md and the folder at commit 829d030. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Qe Context Driven Testing loads about 1.7k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 582 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from proffesor-for-testing/agentic-qe at commit 829d030, republished under its MIT licence (© proffesor-for-testing). 582 words, ~1,664 tokens.

Download SKILL.mdSave it as .claude/skills/qe-context-driven-testing/SKILL.md (or your agent's skills folder).
name
qe-context-driven-testing
description
Apply context-driven testing principles where practices are chosen based on project context, not universal 'best practices'. Use when making testing decisions, questioning dogma, or adapting approaches to specific project needs.
inclusion
auto
tags
context-driven, rst, exploratory, heuristics, oracles, skilled-testing

Context-Driven Testing

<default_to_action> When making testing decisions or adapting approaches:

  1. ANALYZE context: project goals, constraints, risks, team skills
  2. QUESTION practices: "Why this? What risk does it address? What's the cost?"
  3. INVESTIGATE not just check: Does software solve the problem, or create new ones?
  4. ADAPT approach based on context, not "best practices"
  5. DOCUMENT discoveries, not pre-written plans

Quick Context Analysis:

  • Mission: "Find important problems fast enough to matter" (not "execute test cases")
  • Risk: Safety-critical = high rigor; internal tool = lighter touch
  • Constraints: Startup with tight timeline ≠ enterprise with compliance
  • Skills: Novice needs structure; expert adapts intuitively

Critical Success Factors:

  • No "best practices" work everywhere - only good practices in context
  • Testing is investigation, not script execution
  • Context changes; your approach should too </default_to_action>

Quick Reference Card

When to Use
  • Making testing decisions for new project
  • Questioning "that's how it's done" dogma
  • Adapting approach to specific constraints
  • Exploratory testing sessions
Seven Context-Driven Principles
  1. Value of any practice depends on its context
  2. Good practices in context, no universal best practices
  3. People working together are most important
  4. Projects unfold in unpredictable ways
  5. Product is a solution - if problem not solved, product fails
  6. Good testing is challenging intellectual work
  7. Judgment and skill determine right things at right times
Context Factors
FactorQuestions
ProjectBusiness goal? User needs? Failure impact?
ConstraintsTimeline? Budget? Team skills? Legacy?
RiskSafety-critical? Regulated? High volume?
TechnicalStack quirks? Integrations? Observability?
RST Heuristics
HeuristicApplication
SFDIPOTStructure, Function, Data, Interfaces, Platform, Operations, Time
OraclesConsistency with history, similar products, expectations, docs
ToursBusiness District, Historical, Bad Neighborhood, Tourist, Museum

Context-Driven Decisions

Example: Test Automation Level

Startup Context:

  • Small team, rapid changes, unclear product-market fit
  • Decision: Light automation on critical paths, heavy exploratory
  • Rationale: Requirements change too fast for extensive automation

Enterprise Context:

  • Stable features, regulatory requirements, large team
  • Decision: Comprehensive automated regression suite
  • Rationale: Stability allows automation investment to pay off
Example: Documentation

Regulated (FDA/medical):

  • Decision: Detailed test protocols, traceability matrices
  • Rationale: Regulatory compliance isn't optional

Fast-paced startup:

  • Decision: Lightweight session notes, risk logs
  • Rationale: Bureaucracy slows more than it helps
Show full SKILL.md (232 more words)Show less

Investigation vs. Checking

CheckingTesting (Investigation)
Did API return 200?Does API meet user needs?
Does button work?What happens under load?
Match the spec?Does it solve the problem?

Red Flags: Not Context-Driven

  • Follow process "because that's how it's done"
  • Can't explain why you're doing something
  • Measure test cases executed, not problems found
  • Test plan could apply to any project
  • Stop thinking once you have a script

Agent-Assisted Context-Driven Testing

typescript
// Agent analyzes context and recommends approach
const context = await Task("Analyze Context", {
  project: 'e-commerce-platform',
  stage: 'startup',
  constraints: ['timeline: tight', 'budget: limited'],
  risks: ['payment-security', 'high-volume']
}, "qe-fleet-commander");

// Context-aware agent selection
// - qe-security-scanner (critical risk)
// - qe-performance-tester (high volume)
// - Skip: qe-visual-tester (low priority in startup context)

// Adaptive testing strategy
await Task("Generate Tests", {
  context: 'startup',
  focus: 'critical-paths-only',
  depth: 'smoke-tests',
  automation: 'minimal'
}, "qe-test-generator");

Agent Coordination Hints

Memory Namespace
aqe/context-driven/
├── context-analysis/*    - Project context snapshots
├── decisions/*           - Testing decisions with rationale
├── discoveries/*         - What was learned during testing
└── adaptations/*         - How approach changed over time
Fleet Coordination
typescript
const contextFleet = await FleetManager.coordinate({
  strategy: 'context-driven',
  context: {
    type: 'greenfield-saas',
    stage: 'growth',
    compliance: 'gdpr-only'
  },
  agents: ['qe-test-generator', 'qe-security-scanner', 'qe-performance-tester'],
  exclude: ['qe-visual-tester', 'qe-requirements-validator']  // Not priority
});

Practical Tips

  1. Start with risk assessment - List features, ask: How likely to fail? How bad? How hard to test?
  2. Time-box exploration - 2 hours checkout, 30 min error handling, 15 min per browser
  3. Document discoveries - Not "Enter invalid email, verify error" but "Payment API returns 500 instead of 400, no user-visible error. Bug filed."
  4. Talk to humans - Developers, users, support, product
  5. Pair with others - Different perspectives = different bugs

Remember

Context drives decisions. No universal best practices. Skilled testers make informed decisions based on specific goals, constraints, and risks.

You're not a test script executor. You're a skilled investigator helping teams build better products.

With Agents: Agents analyze context, adapt strategies, and learn what works in your situation. Use agents to scale context-driven thinking while maintaining human judgment for critical decisions.

© proffesor-for-testing, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .kiro/skills/qe-context-driven-testing of proffesor-for-testing/agentic-qe.

Open the folder on GitHubat commit 829d030

Compare with similar skills

Qe Context Driven Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Qe Context Driven Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Qe Context Driven Testing this skillproffesor-for-testing/agentic-qe494—~1.7kAutomated safety check: PassMIT
Principle Redesign From First Principlescursor/plugins10k8 repos~211Automated safety check: PassNone
Uxui Principlessickn33/agentic-awesome-skills47k2 repos~548Automated safety check: PassMIT
First Principles Thinkingmindfold-ai/Trellis15k—~4.1kAutomated safety check: PassMIT
Editorial Burgundy Principles Templatenexu-io/open-design100k—~461Automated safety check: PassApache-2.0
Design PrinciplesOwl-Listener/designer-skills2.9k1 repos~300Automated safety check: PassMIT

Similar skills

  • Uxui Principles

    sickn33/agentic-awesome-skills

    Evaluate interfaces against 168 research-backed UX/UI principles, detect antipatterns, and inject UX context into AI coding sessions.

    47k GitHub starsUsed in 2 repos~548 tokens
    Auto-check passed

  • First Principles Thinking

    mindfold-ai/Trellis

    Systematic first principles thinking for any problem domain.

    15k GitHub stars~4.1k tokensUpdated 8 days ago
    DevelopmentAuto-check passed

  • Editorial Burgundy Principles Template

    nexu-io/open-design

    Editorial studio deck template in burgundy / blush / muted-gold palette.

    100k GitHub stars~461 tokensUpdated yesterday
    Documents & OfficeAuto-check passed

  • Design Principles

    Owl-Listener/designer-skills

    Define actionable principles that resolve trade-offs when the team disagrees.

    2.9k GitHub starsUsed in 1 repo~300 tokens
    Auto-check passed

  • Animation Principles

    Owl-Listener/designer-skills

    Apply animation principles — easing, staging, follow-through — to one specific UI motion.

    2.9k GitHub starsUsed in 1 repo~492 tokens
    Frontend & DesignAuto-check passed

More from proffesor-for-testing/agentic-qe

All 111 skills in this repo

  • Contract Testing

    proffesor-for-testing/agentic-qe

    Consumer-driven contract testing for microservices using Pact, schema validation, API versioning, and backward compatibility testing.

    494 GitHub stars~1.8k tokensUpdated 3 days ago
    Auto-check passed

  • Mutation Testing

    proffesor-for-testing/agentic-qe

    Test quality validation through mutation testing, assessing test suite effectiveness by introducing code mutations and measuring kill rate.

    494 GitHub stars~1.7k tokensUpdated 3 days ago
    Auto-check passed

  • Performance Testing

    proffesor-for-testing/agentic-qe

    Profiles application performance under load using k6, Artillery, or JMeter to measure latency, throughput, and error rates.

    494 GitHub stars~2.4k tokensUpdated 3 days ago
    Auto-check passed

  • Code Review Quality

    proffesor-for-testing/agentic-qe

    Conduct context-driven code reviews focusing on quality, testability, and maintainability.

    494 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • Security Testing

    proffesor-for-testing/agentic-qe

    Scans for security vulnerabilities including XSS, SQL injection, CSRF, and auth flaws using OWASP Top 10 methodology.

    494 GitHub stars~2.7k tokensUpdated 3 days ago
    Auto-check: notes

  • Database Testing

    proffesor-for-testing/agentic-qe

    Database schema validation, data integrity testing, migration testing, transaction isolation, and query performance.

    494 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

Questions about Qe Context Driven Testing

What does Qe Context Driven Testing do?

Apply context-driven testing principles where practices are chosen based on project context, not universal 'best practices'. Qe Context Driven Testing is an agent skill from proffesor-for-testing/agentic-qe. Apply context-driven testing principles where practices are chosen based on project context, not universal 'best practices'.

When should I use Qe Context Driven Testing?

Qe Context Driven Testing fits situations like: making testing decisions; questioning dogma; adapting approaches to specific project needs.

How do I install Qe Context Driven Testing in Claude Code?

Run `npx skills add proffesor-for-testing/agentic-qe --skill qe-context-driven-testing -a claude-code`. Or copy the skill folder (.kiro/skills/qe-context-driven-testing in proffesor-for-testing/agentic-qe) into .claude/skills/qe-context-driven-testing in your project. Claude Code loads it when a task matches its description.

How do I install Qe Context Driven Testing in Codex?

Run `npx skills add proffesor-for-testing/agentic-qe --skill qe-context-driven-testing -a codex`. Or copy the skill folder (.kiro/skills/qe-context-driven-testing in proffesor-for-testing/agentic-qe) into .agents/skills/qe-context-driven-testing in your project. Codex loads it when a task matches its description.

Can I use Qe Context Driven Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add proffesor-for-testing/agentic-qe --skill qe-context-driven-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qe-context-driven-testing, .gemini/skills/qe-context-driven-testing, .github/skills/qe-context-driven-testing and .opencode/skills/qe-context-driven-testing in your project.

What does Qe Context Driven Testing need to run?

SKILL.md names no scripts, command-line tools or credentials: Qe Context Driven Testing is instructions for the agent only.

Does Qe Context Driven Testing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Qe Context Driven Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Qe Context Driven Testing use?

Qe Context Driven Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Qe Context Driven Testing use?

About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Qe Context Driven Testing?

Skills that share tags, products or a category with Qe Context Driven Testing: Principle Redesign From First Principles (cursor/plugins, 10k stars), Uxui Principles (sickn33/agentic-awesome-skills, 47k stars), First Principles Thinking (mindfold-ai/Trellis, 15k stars) and Editorial Burgundy Principles Template (nexu-io/open-design, 100k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Qe Context Driven Testing?

proffesor-for-testing (a GitHub user) maintains it in proffesor-for-testing/agentic-qe, which has 494 GitHub stars. The repository holds 111 skills in this directory. The repository was last updated on October 4, 2026.

Source: proffesor-for-testing/agentic-qe on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.