Reproduce Chat States
different-ai/openwork
Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.
Perform quality assurance on code changes after the research-phase - plan-phase - execute-phase workflow.
Install QA From Execute
$ npx skills add alchemiststudiosDOTai/harness-engineering --skill qa-from-execute -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alchemiststudiosDOTai/harness-engineering qa-from-execute --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/alchemiststudiosDOTai/harness-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/qa-from-execute .claude/skills/qa-from-execute && rm -rf skills-srcUse ~/.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/
Install the "qa-from-execute" agent skill from https://github.com/alchemiststudiosDOTai/harness-engineering/tree/main/skills/qa-from-execute into .claude/skills/qa-from-execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-from-execute", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/alchemiststudiosDOTai/harness-engineering/tree/main/skills/qa-from-executeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add alchemiststudiosDOTai/harness-engineering --skill qa-from-execute -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alchemiststudiosDOTai/harness-engineering qa-from-execute --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alchemiststudiosDOTai/harness-engineering.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/qa-from-execute .agents/skills/qa-from-execute && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "qa-from-execute" agent skill from https://github.com/alchemiststudiosDOTai/harness-engineering/tree/main/skills/qa-from-execute into .agents/skills/qa-from-execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-from-execute", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alchemiststudiosDOTai/harness-engineering --skill qa-from-execute -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alchemiststudiosDOTai/harness-engineering qa-from-execute --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alchemiststudiosDOTai/harness-engineering.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/qa-from-execute .cursor/skills/qa-from-execute && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "qa-from-execute" agent skill from https://github.com/alchemiststudiosDOTai/harness-engineering/tree/main/skills/qa-from-execute into .cursor/skills/qa-from-execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-from-execute", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/alchemiststudiosDOTai/harness-engineering.git --path skills/qa-from-execute--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add alchemiststudiosDOTai/harness-engineering --skill qa-from-execute -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alchemiststudiosDOTai/harness-engineering qa-from-execute --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alchemiststudiosDOTai/harness-engineering.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/qa-from-execute .gemini/skills/qa-from-execute && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "qa-from-execute" agent skill from https://github.com/alchemiststudiosDOTai/harness-engineering/tree/main/skills/qa-from-execute into .gemini/skills/qa-from-execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-from-execute", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install alchemiststudiosDOTai/harness-engineering qa-from-executeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add alchemiststudiosDOTai/harness-engineering --skill qa-from-execute -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alchemiststudiosDOTai/harness-engineering.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/qa-from-execute .github/skills/qa-from-execute && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "qa-from-execute" agent skill from https://github.com/alchemiststudiosDOTai/harness-engineering/tree/main/skills/qa-from-execute into .github/skills/qa-from-execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-from-execute", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alchemiststudiosDOTai/harness-engineering --skill qa-from-execute -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alchemiststudiosDOTai/harness-engineering qa-from-execute --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alchemiststudiosDOTai/harness-engineering.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/qa-from-execute .opencode/skills/qa-from-execute && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "qa-from-execute" agent skill from https://github.com/alchemiststudiosDOTai/harness-engineering/tree/main/skills/qa-from-execute into .opencode/skills/qa-from-execute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qa-from-execute", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
qa-from-execute- GitHub stars
- 105
- Token cost
- ~2.5k tokens
- SKILL.md length
- 841 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
Perform quality assurance on code changes after the research-phase - plan-phase - execute-phase workflow.
- Works in 6 steps: Load Execute Context → Identify Changed Areas → Apply QA Checklist Per Changed Area → …
- Tasks that involve QA and bug reports
- SKILL.md covers CRITICAL BOUNDARIES, When to Use, Workflow and Finding Severity Levels, plus 3 more sections
- Calls mypy, npm and jq
What it does
QA From Execute is an agent skill from alchemiststudiosDOTai/harness-engineering. Perform quality assurance on code changes after the research-phase - plan-phase - execute-phase workflow. STRICTLY QA only—no coding, no fixes, no source-code changes. Focus on changed areas only, emphasizing control/data flow correctness.
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering QA and bug reports. The repository describes itself as: harness-engineering discussion of shortcuts, automation, hacks and overall productivity with code agents like claude code, codex, and other harness. The licence is MIT.
When your agent uses it
- Tasks that involve QA and bug reports
Example prompts
- “/qa-from-execute”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Edit, Bash
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 7a9fa15. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBash
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
mypynpmjqpytest
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
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
QA From Execute loads about 2.5k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 841 words of instructions outside code blocks.
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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Write, Edit, Bash
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 alchemiststudiosDOTai/harness-engineering at commit 7a9fa15, republished under its MIT licence (© alchemiststudiosDOTai). 841 words, ~2,542 tokens.
Download SKILL.mdSave it as
.claude/skills/qa-from-execute/SKILL.md (or your agent's skills folder).- name
- qa-from-execute
- description
- Perform quality assurance on code changes after the research-phase -> plan-phase -> execute-phase workflow. STRICTLY QA only—no coding, no fixes, no source-code changes. Focus on changed areas only, emphasizing control/data flow correctness.
- allowed-tools
- Read, Write, Edit, Bash
- writes-to
- memory-bank/qa/
- hard-guards
- QA only - no coding or source-code changes, Write QA output to memory-bank/qa/, Review only the scope captured in memory-bank/execute/
QA From Execute
Evaluate code changes for correctness, risks, and quality. This skill performs read-only analysis of implemented work, producing a QA report without modifying code.
CRITICAL BOUNDARIES
| Activity | Status |
|---|---|
| QA Analysis | ✅ This skill |
| Code Changes | ❌ NO — Read only |
| Bug Fixes | ❌ NO — Report only |
| Execute | ❌ NO — Analysis only |
This skill is STRICTLY for QA evaluation. Do not write code, do not fix issues, and do not perform the Execute phase. Analyze, evaluate, and report.
When to Use
Use this skill when:
- The Execute phase is complete
- Code has been written and needs quality evaluation
- The task is to assess correctness of changes, not modify them
- Pre-merge or post-implementation review is needed
Workflow
Step 1: Load Execute Context
Locate and read the execution log:
- If a path is provided: Read from
memory-bank/execute/<path> - If a topic is provided: Find the latest matching file in
memory-bank/execute/
Extract:
- Which files were modified
- Which functions/endpoints were added or changed
- What the acceptance criteria were
- Any issues encountered during the Execute phase
Step 2: Identify Changed Areas
From the execution log, build a list of:
- Files modified: Paths to all changed files
- Functions changed: Public functions that were added or modified
- Interfaces changed: API endpoints, CLI commands, public methods
- State changes: Database schema, configuration, shared resources
Focus analysis ONLY on these changed areas. Do not review unchanged code.
Step 3: Apply QA Checklist Per Changed Area
For each changed file/function/endpoint, evaluate:
3.1 Inputs & Preconditions
| Check | Question |
|---|---|
| Validation | Are all inputs validated before use? |
| Type safety | Are type assumptions explicit and checked? |
| Null/empty | Are null, undefined, and empty cases handled? |
| Boundaries | Are min/max values, sizes, and limits enforced? |
3.2 Control Flow
| Check | Question |
|---|---|
| Branch coverage | Are all branches reachable? Any dead code? |
| Fall-through | Are switch/case fall-throughs intentional? |
| Early returns | Are guard clauses used appropriately? |
| Loop termination | Do all loops have guaranteed termination? |
3.3 Data Flow
| Check | Question |
|---|---|
| Invariants | Are invariants preserved through transformations? |
| Mutation scope | Is mutation limited to appropriate scope? |
| Shared state | Is shared state access properly synchronized? |
| Aliasing | Are aliasing risks (multiple refs to same data) handled? |
3.4 State & Transactions
| Check | Question |
|---|---|
| Idempotency | Is the operation safe to retry? |
| Atomicity | Are multi-step operations atomic? |
| Rollback | Is there a path to undo partial changes? |
| Concurrency | Are race conditions handled? |
3.5 Error Handling
| Check | Question |
|---|---|
| Specificity | Are exceptions specific (not broad catches)? |
| Retry logic | Is transient failure handled with backoff? |
| Dead letter | Are unprocessable items routed to DLQ/log? |
| Error context | Do errors include sufficient debugging info? |
3.6 Contracts
| Check | Question |
|---|---|
| Pre-conditions | Are pre-conditions documented and enforced? |
| Post-conditions | Are post-conditions guaranteed on success? |
| Schema drift | Do request/response schemas match implementation? |
| Versioning | Are breaking changes properly versioned? |
3.7 Time & Locale
| Check | Question |
|---|---|
| Timezones | Are datetime operations timezone-aware? |
| Monotonic time | Is elapsed time measured with monotonic clocks? |
| DST | Are daylight saving time transitions handled? |
| Format stability | Are date/time formats consistent and unambiguous? |
3.8 Resource Hygiene
| Check | Question |
|---|---|
| File lifecycle | Are files opened/closed properly (with statements)? |
| Connection pooling | Are connections returned to pools? |
| Timeouts | Do all blocking operations have timeouts? |
| Cancellation | Is cancellation propagated through async chains? |
Show full SKILL.md (335 more words)Show less
3.9 Edge Cases
| Check | Question |
|---|---|
| Empty inputs | Is empty/null input handled gracefully? |
| Max sizes | Are large inputs bounded (pagination, limits)? |
| Partial failure | Is partial failure detectable and recoverable? |
| Resource exhaustion | Are OOM, disk full, quota exceeded handled? |
3.10 Public Surface
| Check | Question |
|---|---|
| Backward compat | Are breaking changes intentional and documented? |
| OpenAPI alignment | Do implementations match OpenAPI/JSON schemas? |
| Type exports | Are public types exported and documented? |
| Deprecation | Are deprecated items marked and alternatives provided? |
Step 4: Test & Contracts Analysis
For each changed public function/endpoint:
Map to test coverage
- Run:
pytest -qor equivalent - Run:
coverage run -m pytest && coverage report --format=markdown - Identify which changed functions have tests
- Run:
Identify missing test cases
- Error branches: Are failure paths tested?
- Boundary conditions: Are min/max values tested?
- Property invariants: Are data guarantees verified?
- Mutation tests: Would incorrect code fail tests?
Contract/API verification
- Compare OpenAPI/JSON schema to implementation
- Verify request/response DTOs match spec
- Check for breaking field/enum changes
Step 5: Secondary Scans (Optional)
Run static analysis tools (read-only, report results):
# Type checking
mypy . --ignore-missing-imports 2>/dev/null || echo "mypy not available"
# Security scan
bandit -r . -q 2>/dev/null || echo "bandit not available"
# Dependency audit
pip-audit 2>/dev/null || npm audit --json 2>/dev/null | jq '.metadata' || echo "audit not available"Note findings without attempting fixes.
Step 6: Write QA Report
Create memory-bank/qa/YYYY-MM-DD_HH-MM-SS_<topic>_qa.md:
---
title: "<topic> – QA Report"
phase: QA
date: "YYYY-MM-DD HH:MM:SS"
owner: "<agent_or_user>"
parent_execute: "memory-bank/execute/<file>.md"
git_commit_at_qa: "<sha>"
tags: [qa, <topic>]
---
## Summary
| Metric | Count |
|--------|-------|
| Files reviewed | N |
| Functions reviewed | N |
| CRITICAL findings | N |
| WARNING findings | N |
| INFO findings | N |
| PASS (no issues) | N |
## Changed Areas Reviewed
### File: `path/to/file.py`
| Function/Class | Lines | Status |
|----------------|-------|--------|
| `function_name()` | L45-89 | ⚠️ WARNING |
| `ClassName` | L120-200 | ✅ PASS |
#### Findings for `function_name()`
| Severity | Category | Finding | Recommendation |
|----------|----------|---------|----------------|
| WARNING | Error Handling | Broad `except Exception` catch | Catch specific exceptions |
| INFO | Data Flow | Mutation of input parameter | Document or avoid |
### File: `path/to/another.js`
...
## Test Coverage Analysis
| Function | Has Tests | Coverage % | Missing Cases |
|----------|-----------|------------|---------------|
| `function_name()` | ✅ | 85% | Error branch, empty input |
| `another_function()` | ❌ | 0% | All cases |
## Contract/API Verification
| Endpoint | Schema Match | Breaking Changes |
|----------|--------------|------------------|
| `POST /api/items` | ✅ | None |
| `GET /api/items/:id` | ⚠️ | New required field |
## Static Analysis Summary
| Tool | Result |
|------|--------|
| mypy | N errors, M warnings |
| bandit | N low, M medium issues |
| pip-audit | N vulnerabilities |
## Risk Assessment
| Risk | Likelihood | Impact | Mitigation Status |
|------|------------|--------|-------------------|
| Race condition in shared state | Medium | High | Not mitigated |
| Missing error branch coverage | High | Medium | Not tested |
## Recommendations Summary
### Must Fix (CRITICAL)
1. [Description of critical issue]
### Should Fix (WARNING)
1. [Description of warning]
### Observations (INFO)
1. [Description of observation]Finding Severity Levels
| Level | Definition | Action Required |
|---|---|---|
| CRITICAL | Security risk, data loss, or system instability | Must fix before merge |
| WARNING | Potential bugs, maintainability issues, missing coverage | Should fix, can defer |
| INFO | Style observations, suggestions, notes | Optional |
| PASS | No issues found | None |
Constraints
| Constraint | Rule |
|---|---|
| NO CODE CHANGES | Never write, modify, or delete code |
| NO FIXES | Report issues, do not implement solutions |
| FOCUS ON CHANGES | Only review files listed in the execution log |
| READ-ONLY TOOLS | Use tools that don't modify state |
| DOCUMENT FINDINGS | Every issue must be in the QA report |
Subagent Usage
If additional analysis is needed:
With subagents available: Deploy maximum 3:
| Subagent | When to Deploy |
|---|---|
| antipattern-sniffer | Review changed code for anti-patterns and code smells |
| codebase-analyzer | Deep analysis of specific function implementations |
| context-synthesis | Identify hidden dependencies affected by changes |
Without subagents: Perform manual analysis following the checklist.
Handoff
After writing the QA report to memory-bank/qa/, hand off to the user for disposition.
Suggested next action:
Review memory-bank/qa/<file>.md and decide whether to accept the work or create follow-up planning.© alchemiststudiosDOTai, 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 skills/qa-from-execute of alchemiststudiosDOTai/harness-engineering.
Open the folder on GitHubat commit 7a9fa15
Compare with similar skills
QA From Execute 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| QA From Execute this skillalchemiststudiosDOTai/harness-engineering | 105 | — | ~2.5k | Automated safety check: Notes | MIT | |
| Reproduce Chat Statesdifferent-ai/openwork | 24k | — | ~673 | Automated safety check: Pass | Custom licence | |
| Dynamo Jira TicketDynamoDS/Dynamo | 2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Minimal Run And Auditlllllllama/RigorPilot-Skills | 497 | 2 repos | ~691 | Automated safety check: Pass | MIT | |
| Moav E2EMotherofallVPNs/MoaV | 448 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Anchor Reprolynxlangya/techne | 105 | 1 repos | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Dynamo Jira Ticket
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
Minimal Run And Audit
lllllllama/RigorPilot-Skills
Rigor Run skill for README-first deep learning repo reproduction.
Moav E2E
MotherofallVPNs/MoaV
Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.
Anchor Repro
lynxlangya/techne
Reproduce a behavioral bug before fixing it, record the failing probe, and verify the fix with the same probe.
Creating A Coral Task
Human-Agent-Society/CORAL
Author a new CORAL task — the three pieces that must line up (task.yaml, seed/, a packaged grader/), the coral init → coral validate → smoke-test loop, and how to pick a grader pattern (stdout…
More from alchemiststudiosDOTai/harness-engineering
All 8 skills in this repoAst Grep Setup
alchemiststudiosDOTai/harness-engineering
Set up ast-grep for a codebase with common TypeScript rules for detecting anti-patterns, enforcing best practices, and preventing bugs.
Research Phase
alchemiststudiosDOTai/harness-engineering
This skill should be used when mapping or researching a codebase to understand its structure, patterns, and architecture.
Execute Phase
alchemiststudiosDOTai/harness-engineering
Execute implementation plans from .artifacts/plan/. An agent skill from alchemiststudiosDOTai/harness-engineering.
Harness Map
alchemiststudiosDOTai/harness-engineering
Map a repository's mechanical harness layers: canonical check command, local and CI gates, architecture boundaries, structural rules, behavioral verification, docs ratchets, evidence workflows, and…
Agents Md Mapper
alchemiststudiosDOTai/harness-engineering
This skill should be used when creating, refreshing, or validating a repository AGENTS.md so it stays concise, current, and grounded in repository evidence.
Differential Session Runner
alchemiststudiosDOTai/harness-engineering
Run or continue a differential debugging session between two implementations, traces, captures, or outputs.
Related
Categories
Questions about QA From Execute
What does QA From Execute do?
Perform quality assurance on code changes after the research-phase - plan-phase - execute-phase workflow. QA From Execute is an agent skill from alchemiststudiosDOTai/harness-engineering. Perform quality assurance on code changes after the research-phase - plan-phase - execute-phase workflow.
When should I use QA From Execute?
QA From Execute fits situations like: tasks that involve QA and bug reports.
How do I install QA From Execute in Claude Code?
Run `npx skills add alchemiststudiosDOTai/harness-engineering --skill qa-from-execute -a claude-code`. Or copy the skill folder (skills/qa-from-execute in alchemiststudiosDOTai/harness-engineering) into .claude/skills/qa-from-execute in your project. Claude Code loads it when a task matches its description.
How do I install QA From Execute in Codex?
Run `npx skills add alchemiststudiosDOTai/harness-engineering --skill qa-from-execute -a codex`. Or copy the skill folder (skills/qa-from-execute in alchemiststudiosDOTai/harness-engineering) into .agents/skills/qa-from-execute in your project. Codex loads it when a task matches its description.
Can I use QA From Execute 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 alchemiststudiosDOTai/harness-engineering --skill qa-from-execute -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qa-from-execute, .gemini/skills/qa-from-execute, .github/skills/qa-from-execute and .opencode/skills/qa-from-execute in your project.
What does QA From Execute need to run?
Going by SKILL.md and its folder, QA From Execute needs the command-line tools its instructions call (mypy, npm, jq and pytest). Its frontmatter pre-approves these tools: Read, Write, Edit, Bash.
Does QA From Execute access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is QA From Execute safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does QA From Execute use?
QA From Execute 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 QA From Execute use?
About 2.5k tokens (SKILL.md is roughly 10k 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 QA From Execute?
Skills that share tags, products or a category with QA From Execute: Reproduce Chat States (different-ai/openwork, 24k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars), Minimal Run And Audit (lllllllama/RigorPilot-Skills, 497 stars) and Moav E2E (MotherofallVPNs/MoaV, 448 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains QA From Execute?
alchemiststudiosDOTai (a GitHub organization) maintains it in alchemiststudiosDOTai/harness-engineering, which has 105 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on March 17, 2026.
Source: alchemiststudiosDOTai/harness-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.