SkillAgentSearch skills...

quick

Tracked lightweight execution with composable rigor flags: --trivial, --discuss, --research, --full. Covers zero-ceremony inline fixes (typo, spelling fix, small mistake in a single file, ≤3 edits) through contained multi-file changes.

Install / Use

npx skills add notque/vexjoy-agent --skill quick

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Supported Platforms

Universal

Tags

Our assessment of quick

quick scores 86/100 on our quality scale, 244th of 426 Education & Research skills we index.

Its SKILL.md is 7.4 KB long, well organised into 12 sections with 1 code example: a thorough specification that gives an agent plenty to work with.

It has 425 GitHub stars, a meaningful sign that others use it.

Substance
29/30
Structure
17/20
Description
15/15
Adoption
11/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated yesterday, so quick is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

quick compared with similar skills

All 4 of these similar skills score higher than quick; compare them before choosing.

SkillScoreStarsUpdatedFormat
quick (this skill)by notque864251d agoSKILL.md
last30days-skillby mvanhorn10063.5k3d agoCLAUDE.md
algorithmic-artby anthropics100177.9k12d agoSKILL.md
pptxby anthropics100177.9k12d agoSKILL.md
designby nextlevelbuilder100130.2k13d agoSKILL.md

Frequently asked questions

How do I install quick?
Run npx skills add notque/vexjoy-agent --skill quick. The install tabs above show the steps for each supported agent.
Which AI agents does quick work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is quick safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is quick still maintained?
The repository was last updated yesterday, so quick is actively maintained.

name: quick description: "Tracked lightweight execution with composable rigor flags: --trivial, --discuss, --research, --full. Covers zero-ceremony inline fixes (typo, spelling fix, small mistake in a single file, ≤3 edits) through contained multi-file changes." user-invocable: true argument-hint: "[--trivial] [--discuss] [--research] [--full] <task>" allowed-tools:

  • Read
  • Write
  • Edit
  • Bash
  • Grep
  • Glob
  • Skill
  • Task routing: force_route: true triggers:
    • quick task
    • small change
    • ad hoc task
    • add a flag
    • small refactor
    • targeted fix
    • quick fix
    • typo fix
    • fix typo
    • fix the typo
    • one-line change
    • trivial fix
    • rename variable
    • rename this variable
    • update value
    • fix import
    • small mistake
    • small mistake in
    • mistake in spelling
    • spelling mistake
    • spelling fix
    • fix the spelling
    • typo in
    • small fix in
    • small fix
    • tiny fix not_for: "'quick' as speed preference, general bug diagnosis requiring investigation" complexity: Simple category: process

/quick

Make contained changes in one execution thread. Use /do for multiple components, architectural changes, or parallel work. Keep plans inline; do not create task_plan.md.

Flags

All flags default off. Combine discussion, research, and verification as needed.

| Flag | Effect | |---|---| | --trivial | Mechanical fix: at most 3 edits across at most 3 files; no displayed plan, task ID, or subagents. | | --discuss | Resolve independent ambiguities together before planning. | | --interview | Resolve dependent decisions one question at a time, with a recommendation. | | --research | Investigate unfamiliar code before planning. | | --full | Verify the plan, then run affected tests, configured lint, and diff review. | | --no-branch | Stay on the current branch if repository branch rules permit it. | | --no-commit | Leave edits uncommitted, including in trivial mode. |

Deep References

| When | Load | Content | |---|---|---| | Emitting banners, commit format, STATE.md entries | references/templates.md | Output and tracking contracts |

Setup

Read repository CLAUDE.md unless already loaded and current. Parse flags; the remaining text is the task. Follow existing authorization and repository constraints throughout.

Check the branch during setup. Never let --trivial or --no-branch bypass branch safety. For trivial work on main/master, create quick/<brief-description>; for standard work, create quick/<task-id>-<brief-kebab-description> after assigning the ID in step 2 and before editing, unless --no-branch is allowed. Preserve unrelated changes.

Trivial mode

Use for --trivial or a clearly mechanical one-line change identified by the router.

  1. Read the targets and check scope. Investigation or unfamiliar behavior requires /quick --research; more than 3 files, new package imports, or dependency-file changes require standard /quick. For ambiguity, ask one clarifying question; if unresolved, use /quick --discuss.
  2. Edit directly and count edits. If more than 3 are needed, preserve completed work and continue standard /quick. Explain the scope change and carry forward the original request and completed edits.
  3. Review the diff and run applicable repository checks. Stage only intended files with git add <specific-files> and commit using references/templates.md, unless --no-commit applies.
  4. Emit the trivial summary and stop. Report an omitted commit as skipped, never as successful.

Standard procedure

1. Resolve decisions and investigate

Use discussion for --discuss or material uncertainty about the requested change, approach, or acceptance criteria. Batch independent questions using the DISCUSS template. Wait for answers needed to proceed; do not ask again about decisions or actions already authorized.

For --research or unfamiliar code, read relevant source, tests, and configuration. Establish current behavior, where the change fits, and what could break. Summarize findings and their effect on the plan in 3–5 lines.

2. Plan and assign an ID

Use YYMMDD-xxx, with a Base36 sequence: 001 through 009, 00a through 00z, then 010.

date_prefix=$(date +%y%m%d)

Increment today's highest sequence in root STATE.md, starting at 001 if absent. If corrupted, recover the sequence from git log entries matching Quick task YYMMDD-. Increment again on branch-name collision.

Display the inline plan from references/templates.md: intended edits, files, rationale, and estimated edit count. Create the branch under the setup rules. With --full, verify that the plan meets acceptance criteria before editing. Recommend --full for security, payments, or data migration.

3. Execute and watch scope

Make the planned edits and track their count. Above 15 estimated edits, suggest /do. Warn at 10 actual edits and reassess at 15. These standard-mode thresholds are advisory; continue within established authorization when the work remains contained. Ask only when a scope decision is unresolved. Trivial mode's 3-edit limit remains strict.

For base verification, run an appropriate syntax/build check, such as python3 -m py_compile <files>, go build ./..., or tsc --noEmit, plus required repository checks.

With --full, run tests for affected packages/modules, configured lint on changed files, and git diff review for unintended changes, missing error handling, and broken imports. Run the full suite when required by the repository or requested by the user. Fix relevant failures before claiming completion; report unrelated blockers accurately.

4. Commit and log

Unless --no-commit, stage specific intended files with git add <specific-files>, use the conventional commit format from references/templates.md, and include Quick task <task-id> in the body. Verify with git log -1 --oneline.

Create or append to root STATE.md using the reference schema. Use tier trivial->quick after escalation; otherwise quick. Record skipped commits explicitly. Emit the completion summary with changes, checks, commit or skipped status, branch, flags, and log location. Continue any already-authorized delivery steps.

Examples

Base mode: /quick add --verbose flag to the CLI -- Generate ID 260322-001, plan 3 edits (flag definition, handler, help text), create branch quick/260322-001-add-verbose-flag, execute, commit, log.

With research: /quick --research fix the timeout bug in auth middleware -- Read auth middleware first, trace call path, then plan and execute.

Escalated from trivial: --trivial hit 3-edit limit across 5 files. Quick picks up with context, plans remaining edits, commits all changes, logs as tier trivial->quick.

Full rigor: /quick --full update payment amount rounding logic -- Plan edit, execute, run tests + lint + diff review, commit.

Error Handling

| Error | Cause | Fix | |---|---|---| | Task ID collision | Two tasks with same sequence | Increment sequence. If STATE.md corrupted, scan git log for Quick task YYMMDD- to find next ID. | | Scope exceeds quick tier | Task grows beyond contained work | Suggest /do for multi-component or architectural changes. >15 edits is advisory. | | Test failure in --full mode | Quality gate found issues | Fix failing tests. If fix needs significant work, note in STATE.md and suggest follow-up /quick. | | Branch conflict | Branch quick/<id>-... exists | Increment task ID sequence and retry. |

Related Skills

View on GitHub
GitHub Stars425
CategoryEducation
Updated1d ago
Forks48

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions