Skip to main content
Run any Skill in Manus
with one click
GitHub repository

termcanvas

termcanvas contains 7 collected skills from blueberrycongee, with repository-level occupation coverage and site-owned skill detail pages.

skills collected
7
Stars
340
updated
2026-04-12
Forks
23
Occupation coverage
5 occupation categories · 100% classified
repository explorer

Skills in this repository

code-review
software-quality-assurance-analysts-and-testers

Structured code review skill. Use when asked to "review this code", "review this PR", "check this diff", or when acting as a Hydra reviewer. Runs a multi-pass review with specialist focus areas and confidence-gated findings.

2026-04-12
qa
software-quality-assurance-analysts-and-testers

QA testing skill with real browser automation. Use when asked to "test this site", "QA this page", "check for visual bugs", "verify the deploy", or when Hydra needs browser validation for UI changes. Requires the browse binary.

2026-04-12
using-termcanvas
computer-occupations-all-other

Use when starting work in a TermCanvas-managed repo to route between direct work, Hydra, or a narrow TermCanvas skill.

2026-04-12
hydra
computer-occupations-all-other

Use when a task should run through Hydra's Lead-driven workflow for multi-agent orchestration, or when an existing workflow must be inspected or cleaned up.

2026-04-11
challenge
project-management-specialists

Adversarial review skill. Use when the user wants to stress-test an idea, argument, proposal, or opinion from multiple independent angles. Spawns parallel Hydra workers with orthogonal analytical methodologies.

2026-04-08
security-audit
information-security-analysts

Security audit skill. Use when asked to "audit security", "check for vulnerabilities", "security review", "pentest", or when evaluating code that handles auth, user input, secrets, or external data. Runs a phased scan covering OWASP Top 10 and STRIDE threat modeling.

2026-03-31
investigate
software-developers

Systematic debugging skill. Use when encountering a bug, test failure, unexpected behavior, or when asked to "investigate", "debug", "diagnose", or "figure out why". Enforces root-cause-first discipline with structured hypothesis tracking.

2026-03-31