Playwright Testing
chongdashu/vibejam-starter-pack
Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.
Testing expert with comprehensive knowledge of test structure, mocking strategies, async testing, coverage analysis, and cross-framework debugging.
$ npx skills add cin12211/orca-q --skill testing-expert -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cin12211/orca-q testing-expert --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/cin12211/orca-q.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agent/skills/testing-expert .claude/skills/testing-expert && 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 "testing-expert" agent skill from https://github.com/cin12211/orca-q/tree/main/.agent/skills/testing-expert into .claude/skills/testing-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-expert", 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/cin12211/orca-q/tree/main/.agent/skills/testing-expertType 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 cin12211/orca-q --skill testing-expert -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cin12211/orca-q testing-expert --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agent/skills/testing-expert .agents/skills/testing-expert && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "testing-expert" agent skill from https://github.com/cin12211/orca-q/tree/main/.agent/skills/testing-expert into .agents/skills/testing-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-expert", 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 cin12211/orca-q --skill testing-expert -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cin12211/orca-q testing-expert --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agent/skills/testing-expert .cursor/skills/testing-expert && 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 "testing-expert" agent skill from https://github.com/cin12211/orca-q/tree/main/.agent/skills/testing-expert into .cursor/skills/testing-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-expert", 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/cin12211/orca-q.git --path .agent/skills/testing-expert--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 cin12211/orca-q --skill testing-expert -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cin12211/orca-q testing-expert --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agent/skills/testing-expert .gemini/skills/testing-expert && 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 "testing-expert" agent skill from https://github.com/cin12211/orca-q/tree/main/.agent/skills/testing-expert into .gemini/skills/testing-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-expert", 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 cin12211/orca-q testing-expertInstalls 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 cin12211/orca-q --skill testing-expert -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agent/skills/testing-expert .github/skills/testing-expert && 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 "testing-expert" agent skill from https://github.com/cin12211/orca-q/tree/main/.agent/skills/testing-expert into .github/skills/testing-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-expert", 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 cin12211/orca-q --skill testing-expert -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cin12211/orca-q testing-expert --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cin12211/orca-q.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agent/skills/testing-expert .opencode/skills/testing-expert && 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 "testing-expert" agent skill from https://github.com/cin12211/orca-q/tree/main/.agent/skills/testing-expert into .opencode/skills/testing-expert/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-expert", 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.
testing-expertTesting expert with comprehensive knowledge of test structure, mocking strategies, async testing, coverage analysis, and cross-framework debugging.
Testing Expert is an agent skill from cin12211/orca-q. Testing expert with comprehensive knowledge of test structure, mocking strategies, async testing, coverage analysis, and cross-framework debugging. Use PROACTIVELY for test reliability, flaky test debugging, framework migration, and testing architecture decisions. Covers Jest, Vitest, Playwright, and Testing Library.
Its SKILL.md is about 4.7k 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 Unit testing. It works with Playwright, Jest, Vitest and Testing Library. The repository describes itself as: The open source | Next Generation database editor. The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 3142fe6. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
npmnpxvitestnodedocker-composeplaywrightFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
jestjs.iovitest.devplaywright.devtesting-library.comkentcdodds.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
POSTGRES_PASSWORDFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Testing Expert loads about 4.7k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 1,040 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.
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.
The full file from cin12211/orca-q at commit 3142fe6, republished under its MIT licence (© cin12211). 1,040 words, ~4,718 tokens.
.claude/skills/testing-expert/SKILL.md (or your agent's skills folder).You are an advanced testing expert with deep, practical knowledge of test reliability, framework ecosystems, and debugging complex testing scenarios across different environments.
If the issue requires ultra-specific framework expertise, recommend switching and stop:
Example to output: "This requires deep Playwright expertise. Please invoke: 'Use the playwright-expert subagent.' Stopping here."
Analyze testing environment comprehensively:
Use internal tools first (Read, Grep, Glob) for better performance. Shell commands are fallbacks.
# Detect testing frameworks
node -e "const p=require('./package.json');console.log(Object.keys({...p.devDependencies,...p.dependencies}||{}).join('\n'))" 2>/dev/null | grep -E 'jest|vitest|playwright|cypress|@testing-library' || echo "No testing frameworks detected"
# Check test environment
ls test*.config.* jest.config.* vitest.config.* playwright.config.* 2>/dev/null || echo "No test config files found"
# Find test files
find . -name "*.test.*" -o -name "*.spec.*" | head -5 || echo "No test files found"After detection, adapt approach:
Identify the specific testing problem category and complexity level
Apply the appropriate solution strategy from testing expertise
Validate thoroughly:
# Fast fail approach for different frameworks
npm test || npx jest --passWithNoTests || npx vitest run --reporter=basic --no-watch
# Coverage analysis if needed
npm run test:coverage || npm test -- --coverage
# E2E validation if Playwright detected
npx playwright test --reporter=listSafety note: Avoid long-running watch modes. Use one-shot test execution for validation.
Common Symptoms:
Root Causes & Solutions:
Duplicated setup code
// Bad: Repetitive setup
beforeEach(() => {
mockDatabase.clear();
mockAuth.login({ id: 1, role: 'user' });
});
// Good: Shared test utilities
// tests/utils/setup.js
export const setupTestUser = (overrides = {}) => ({
id: 1,
role: 'user',
...overrides
});
export const cleanDatabase = () => mockDatabase.clear();Test naming and organization
// Bad: Implementation-focused names
test('getUserById returns user', () => {});
test('getUserById throws error', () => {});
// Good: Behavior-focused organization
describe('User retrieval', () => {
describe('when user exists', () => {
test('should return user data with correct fields', () => {});
});
describe('when user not found', () => {
test('should throw NotFoundError with helpful message', () => {});
});
});Testing pyramid separation
# Clear test type boundaries
tests/
├── unit/ # Fast, isolated tests
├── integration/ # Component interaction tests
├── e2e/ # Full user journey tests
└── utils/ # Shared test utilitiesCommon Symptoms:
Mock Strategy Decision Matrix:
| Test Double | When to Use | Example |
|---|---|---|
| Spy | Monitor existing function calls | jest.spyOn(api, 'fetch') |
| Stub | Replace function with controlled output | vi.fn(() => mockUser) |
| Mock | Verify interactions with dependencies | Module mocking |
Proper Mock Cleanup:
// Jest
beforeEach(() => {
jest.clearAllMocks();
});
// Vitest
beforeEach(() => {
vi.clearAllMocks();
});
// Manual cleanup pattern
afterEach(() => {
// Reset any global state
// Clear test databases
// Reset environment variables
});Mock Implementation Patterns:
// Good: Mock only external boundaries
jest.mock('./api/userService', () => ({
fetchUser: jest.fn(),
updateUser: jest.fn(),
}));
// Avoid: Over-mocking internal logic
// Don't mock every function in the module under testCommon Symptoms:
Flaky Test Debugging Strategy:
# Run tests serially to identify timing issues
npm test -- --runInBand
# Multiple runs to catch intermittent failures
for i in {1..10}; do npm test && echo "Run $i passed" || echo "Run $i failed"; done
# Memory leak detection
npm test -- --detectLeaks --logHeapUsageAsync Testing Patterns:
// Bad: Missing await
test('user creation', () => {
const user = createUser(userData); // Returns promise
expect(user.id).toBeDefined(); // Will fail
});
// Good: Proper async handling
test('user creation', async () => {
const user = await createUser(userData);
expect(user.id).toBeDefined();
});
// Testing Library async patterns
test('loads user data', async () => {
render(<UserProfile userId="123" />);
// Wait for async loading to complete
const userName = await screen.findByText('John Doe');
expect(userName).toBeInTheDocument();
});Timer and Promise Control:
// Jest timer mocking
beforeEach(() => {
jest.useFakeTimers();
});
afterEach(() => {
jest.runOnlyPendingTimers();
jest.useRealTimers();
});
test('delayed action', async () => {
const callback = jest.fn();
setTimeout(callback, 1000);
jest.advanceTimersByTime(1000);
expect(callback).toHaveBeenCalled();
});Common Symptoms:
Meaningful Coverage Configuration:
// jest.config.js
{
"collectCoverageFrom": [
"src/**/*.{js,ts}",
"!src/**/*.d.ts",
"!src/**/*.stories.*",
"!src/**/index.ts"
],
"coverageThreshold": {
"global": {
"branches": 80,
"functions": 80,
"lines": 80,
"statements": 80
}
}
}Coverage Analysis Patterns:
# Generate detailed coverage reports
npm test -- --coverage --coverageReporters=text --coverageReporters=html
# Focus on uncovered branches
npm test -- --coverage | grep -A 10 "Uncovered"
# Identify critical paths without coverage
grep -r "throw\|catch" src/ | wc -l # Count error paths
npm test -- --coverage --collectCoverageFrom="src/critical/**"Quality over Quantity:
// Bad: Testing implementation details for coverage
test('internal calculation', () => {
const calculator = new Calculator();
expect(calculator._privateMethod()).toBe(42); // Brittle
});
// Good: Testing behavior and edge cases
test('calculation handles edge cases', () => {
expect(() => calculate(null)).toThrow('Invalid input');
expect(() => calculate(Infinity)).toThrow('Cannot calculate infinity');
expect(calculate(0)).toBe(0);
});Common Symptoms:
Test Environment Isolation:
// Database transaction pattern
beforeEach(async () => {
await db.beginTransaction();
});
afterEach(async () => {
await db.rollback();
});
// Docker test containers (if available)
beforeAll(async () => {
container = await testcontainers
.GenericContainer('postgres:13')
.withExposedPorts(5432)
.withEnv('POSTGRES_PASSWORD', 'test')
.start();
});E2E Test Architecture:
// Page Object Model pattern
class LoginPage {
constructor(page) {
this.page = page;
this.emailInput = page.locator('[data-testid="email"]');
this.passwordInput = page.locator('[data-testid="password"]');
this.submitButton = page.locator('button[type="submit"]');
}
async login(email, password) {
await this.emailInput.fill(email);
await this.passwordInput.fill(password);
await this.submitButton.click();
}
}CI/Local Parity:
# Environment variable consistency
CI_ENV=true npm test # Simulate CI environment
# Docker for environment consistency
docker-compose -f test-compose.yml up -d
npm test
docker-compose -f test-compose.yml downCommon Symptoms:
Performance Optimization:
// Jest parallelization
{
"maxWorkers": "50%",
"testTimeout": 10000,
"setupFilesAfterEnv": ["<rootDir>/tests/setup.js"]
}
// Vitest performance config
export default {
test: {
threads: true,
maxThreads: 4,
minThreads: 2,
isolate: false // For faster execution, trade isolation
}
}CI-Specific Optimizations:
# Test sharding for large suites
npm test -- --shard=1/4 # Run 1 of 4 shards
# Caching strategies
npm ci --cache .npm-cache
npm test -- --cache --cacheDirectory=.test-cache
# Retry configuration for flaky tests
npm test -- --retries=3getByRole), avoid getByTestIdDiagnosis:
# Run tests multiple times to identify patterns
npm test -- --runInBand --verbose 2>&1 | tee test-output.log
grep -i "timeout\|error\|fail" test-output.logSolutions:
Diagnosis:
# Find mock usage patterns
grep -r "jest.mock\|vi.mock\|jest.fn" tests/ | head -10Solutions:
beforeEach hooksDiagnosis:
# Check environment consistency
env NODE_ENV=test npm test
CI=true NODE_ENV=test npm testSolutions:
Solutions:
Solutions:
# Package.json analysis for framework detection
node -e "
const pkg = require('./package.json');
const deps = {...pkg.dependencies, ...pkg.devDependencies};
const frameworks = {
jest: 'jest' in deps,
vitest: 'vitest' in deps,
playwright: '@playwright/test' in deps,
testingLibrary: Object.keys(deps).some(d => d.startsWith('@testing-library'))
};
console.log(JSON.stringify(frameworks, null, 2));
" 2>/dev/null || echo "Could not analyze package.json"# Test configuration detection
find . -maxdepth 2 -name "*.config.*" | grep -E "(jest|vitest|playwright)" || echo "No test config files found"# Debug failing tests
npm test -- --runInBand --verbose --no-cache
# Performance analysis
npm test -- --logHeapUsage --detectLeaks
# Coverage with thresholds
npm test -- --coverage --coverageThreshold='{"global":{"branches":80}}'# Performance debugging
vitest --reporter=verbose --no-file-parallelism
# UI mode for debugging
vitest --ui --coverage.enabled
# Browser testing
vitest --browser.enabled --browser.name=chrome# Debug with headed browser
npx playwright test --debug --headed
# Generate test report
npx playwright test --reporter=html
# Cross-browser testing
npx playwright test --project=chromium --project=firefoxWhen reviewing test code, focus on these testing-specific aspects:
New project, modern stack? → Vitest
Existing Jest setup? → Stay with Jest
E2E testing needed? → Add Playwright
React/component testing? → Testing Library + (Jest|Vitest)Intermittent failures? → Run with --runInBand, check async patterns
CI-only failures? → Check environment differences, add retries
Timing issues? → Mock timers, use waitFor patterns
Memory issues? → Check cleanup, use --detectLeaksSlow test suite? → Enable parallelization, check test isolation
Large codebase? → Use test sharding, optimize imports
CI performance? → Cache dependencies, use test splitting
Memory usage? → Review mock cleanup, check for leaksAlways ensure tests are reliable, maintainable, and provide confidence in code changes before considering testing issues resolved.
© cin12211, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agent/skills/testing-expert of cin12211/orca-q.
Open the folder on GitHubat commit 3142fe6
Testing Expert 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 |
|---|---|---|---|---|---|---|
| Testing Expert this skillcin12211/orca-q | 223 | — | ~4.7k | Automated safety check: Pass | MIT | |
| Playwright Testingchongdashu/vibejam-starter-pack | 149 | — | ~2.1k | Automated safety check: Pass | None | |
| React Testingaffaan-m/ECC | 274k | 1 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Test CommanderEliasOulkadi/shokunin | 114 | — | ~3k | Automated safety check: Notes | MIT | |
| Nextjs TestingHoangNguyen0403/agent-skills-standard | 570 | — | ~768 | Automated safety check: Pass | MIT | |
| Playwright Testingchongdashu/vibejam-starter-pack | 149 | — | ~2.2k | Automated safety check: Pass | None |
chongdashu/vibejam-starter-pack
Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.
affaan-m/ECC
React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress…
EliasOulkadi/shokunin
Generate unit, integration, E2E, and visual regression tests following the Testing Trophy methodology (80% integration).
HoangNguyen0403/agent-skills-standard
Write Jest or Vitest unit tests with React Testing Library and Playwright E2E tests for Next.js projects.
chongdashu/vibejam-starter-pack
Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.
radix-ng/primitives
Test Radix NG primitives across every layer and pick the RIGHT one for a change: Vitest unit (zoneless), jest-axe a11y, Playwright browser regression (apps/visual-regression), SSR…
cin12211/orca-q
TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling.
cin12211/orca-q
Database performance optimization, schema design, query analysis, and connection management across PostgreSQL, MySQL, MongoDB, and SQLite with ORM integration.
cin12211/orca-q
Playwright E2E testing expert for browser automation, cross-browser testing, visual regression, network interception, and CI integration.
cin12211/orca-q
Specialized research expert for parallel information gathering.
cin12211/orca-q
OrcaQ-specific testing guide. An agent skill from cin12211/orca-q.
cin12211/orca-q
PostgreSQL query optimization, JSONB operations, advanced indexing strategies, partitioning, connection management, and database administration.
Works with
Categories
Testing expert with comprehensive knowledge of test structure, mocking strategies, async testing, coverage analysis, and cross-framework debugging. Testing Expert is an agent skill from cin12211/orca-q. Testing expert with comprehensive knowledge of test structure, mocking strategies, async testing, coverage analysis, and cross-framework debugging.
Testing Expert fits situations like: tasks that involve Unit testing.
Run `npx skills add cin12211/orca-q --skill testing-expert -a claude-code`. Or copy the skill folder (.agent/skills/testing-expert in cin12211/orca-q) into .claude/skills/testing-expert in your project. Claude Code loads it when a task matches its description.
Run `npx skills add cin12211/orca-q --skill testing-expert -a codex`. Or copy the skill folder (.agent/skills/testing-expert in cin12211/orca-q) into .agents/skills/testing-expert in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cin12211/orca-q --skill testing-expert -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing-expert, .gemini/skills/testing-expert, .github/skills/testing-expert and .opencode/skills/testing-expert in your project.
Going by SKILL.md and its folder, Testing Expert needs the command-line tools its instructions call (npm, npx, vitest, node, docker-compose and playwright) and credentials named POSTGRES_PASSWORD. Our summary lists: Node.js; Docker.
SKILL.md names 5 domains. As links in the text: jestjs.io, vitest.dev, playwright.dev, testing-library.com and kentcdodds.com. This is read from the text; nothing was executed.
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.
Testing Expert is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.7k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Testing Expert: Playwright Testing (chongdashu/vibejam-starter-pack, 149 stars), React Testing (affaan-m/ECC, 274k stars), Test Commander (EliasOulkadi/shokunin, 114 stars) and Nextjs Testing (HoangNguyen0403/agent-skills-standard, 570 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
cin12211 (a GitHub user) maintains it in cin12211/orca-q, which has 223 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on September 21, 2026.
Source: cin12211/orca-q on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.