Agent skill

Writing

by notque in notque/vexjoy-agent

Writing: voice creation and validation, prose editing, anti-AI cleanup, professional communication, translation.

MITAuto-check: notesWriting & Content

Install Writing

skills CLI
$ npx skills add notque/vexjoy-agent --skill writing -a claude-code

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

GitHub CLI
$ gh skill install notque/vexjoy-agent writing --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/notque/vexjoy-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/content/writing .claude/skills/writing && 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
writing
GitHub stars
435
Token cost
~3.4k tokens
SKILL.md length
1,317 words
Files
12 (incl. references)
Skills in repo
61
Repo updated
First seen
Licence
MIT

At a glance

Writing: voice creation and validation, prose editing, anti-AI cleanup, professional communication, translation.

  • Works in 12 steps: COLLECT (Gate: 50+ samples) → EXTRACT (Gate: profile.json valid,… → PATTERN (Gate: 10+ phrase fingerprints,… → …
  • Tasks that involve Translation
  • SKILL.md covers Deep References, Mode 1: Voice Writing, Mode 2: Voice Creation and Mode 3: Voice Validation, plus 2 more sections
  • Calls python3

What it does

Writing is an agent skill from notque/vexjoy-agent. Writing: voice creation and validation, prose editing, anti-AI cleanup, professional communication, translation.

Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files (for example `references/cv-extraction-validation.md`, `references/cv-iteration-guide.md` and `references/cv-pattern-identification.md`).

It sits in Writing & Content, covering Translation. The repository describes itself as: VexJoy AI Agent with Jev Intelligent Routing - /do routes plain-English requests to the right specialist agent and gates the work with reviews, tests, and a learning loop. The licence is MIT.

When your agent uses it

  • Tasks that involve Translation

Example prompts

  • “/writing”

Requirements

  • Python 3
  • Pre-approved tools (allowed-tools): Read, Write, Bash, Grep, Glob, Edit, Task, Skill, Agent

Workflow steps

12 steps, taken from the step headings in SKILL.md.

  1. COLLECT (Gate: 50+ samples)
  2. EXTRACT (Gate: profile.json valid, script exit 0)
  3. PATTERN (Gate: 10+ phrase fingerprints, 3+ thinking patterns, 2/4 architectures)
  4. RULE (Gate: 4+ positive traits, 6+ contrastive aspects, 3+ prohibitions)
  5. GENERATE (Gate: SKILL.md 2000+ lines, samples 400+ lines)
  6. VALIDATE (Gate: score >= 60, 0 errors)
  7. ITERATE (Gate: 4/5 authorship match)
  8. IDENTIFY TARGET
  9. SCAN
  10. REVISE
  11. VERIFY
  12. PARSE

What it can do on your machine

Read from SKILL.md and the folder at commit 5218674. 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:

    • Read
    • Write
    • Bash
    • Grep
    • Glob
    • Edit
    • Task
    • Skill
    • Agent

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python3

    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

Writing loads about 3.4k tokens when it runs, and up to ~21k if it reads all its reference files. Until then it costs about 30 tokens; SKILL.md has 1,317 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~30
When it runs · the whole SKILL.md, loaded when a task matches
~3.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~21k

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, Bash, Grep, Glob, Edit, Task, Skill, Agent

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 notque/vexjoy-agent at commit 5218674, republished under its MIT licence (© notque). 1,317 words, ~3,363 tokens.

Download SKILL.mdSave it as .claude/skills/writing/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.
name
writing
description
Writing: voice creation and validation, prose editing, anti-AI cleanup, professional communication, translation.
allowed-tools
Read, Write, Bash, Grep, Glob, Edit, Task, Skill, Agent
user-invocable
true
routing.force_route
true
routing.not_for
code comments (use code-quality), API documentation (use docs-sync-checker), scheduling or calendaring content (use content), code review (use review)
routing.triggers
write article, blog post, write in voice, voice pipeline, voice writer, validate voice, voice fidelity, write email, draft memo, executive summary, status…
routing.category
content
routing.pairs_with
joy-check, content

Writing Skill

Five modes. Match the request to the correct mode and follow its section.

Request matchesMode
Article, blog post, content using a voice profileVoice Writing
Build a voice profile from writing samplesVoice Creation
Check draft against voice profile fidelityVoice Validation
Email, memo, status update, meeting notes, pushbackProfessional Communication
Translate or localize a documentTranslation

Deep References

SignalLoadContent
Narrative validation, 500+ word contentreferences/narrative-patterns.md13-check rubric (StoryScope-derived)
Professional-communication examplesreferences/pc-examples.mdWorked transformation examples
Professional-communication templatesreferences/pc-templates.mdStatus templates, phrase transformations
Voice creation: pattern extractionreferences/cv-pattern-identification.mdPhrase fingerprints, architectures
Voice creation: triple-validationreferences/cv-extraction-validation.mdRecurrence/power/exclusivity rubric
Voice creation: skill file generationreferences/cv-skill-generation.mdSKILL.md structure, frontmatter, samples
Voice creation: rules templatereferences/cv-voice-rules-template.mdPositive/contrastive identity, prohibitions
Voice creation: iteration and authorshipreferences/cv-iteration-guide.mdValidation commands, authorship matching
Voice creation: phase bannersreferences/cv-phase-banners.mdProgress reporting templates
Translation modes, chunkingreferences/tr-modes.mdQuick/normal/refined, parallel dispatch
Translation glossaryreferences/tr-glossary-template.mdGlossary format, term-preservation rules

Mode 1: Voice Writing

13-phase pipeline for voice-profiled articles and blog posts. Each phase runs as a separate agent dispatch. Phase artifacts are files in .voice-phase/, not context between agents.

Set VOICE_WRITER_ACTIVE=1 before dispatching any phase agent.

Phases
  1. LOAD: Identify voice profile. Run ls ~/.claude/skills/ | grep voice- for available profiles. Read profile.json, all references/, and the target site's CLAUDE.md. Output: .voice-phase/01-load.json.

  2. GROUND: Anchor in lived experience. Identify: core problem, personal experience, the "vex" (frustration) and "joy" (resolution), 3-5 concrete details, single reader takeaway. Output: .voice-phase/02-grounding.md.

  3. STATS-CHECKPOINT: Extract target ranges from profile (sentence/paragraph length, pronoun density, contraction rate, banned patterns). Output: .voice-phase/03-stats-baseline.json.

  4. GENERATE: Write the full draft in target voice. Apply narrative structure guidance: let evidence speak, mix emotional registers, weave secondary threads, leave room for uncertainty, reference specifically, vary intensity, include one unpredicted event, acknowledge the reader, vary temporal structure, close with forward motion, subvert one expectation. Target 1200-2000 words. Output: .voice-phase/04-draft.md.

  5. HOOK-GATE: Check opening for at least one concrete number, specific date, or unexpected detail. Score 1-10. If < 8, pull the most surprising finding from the body into the opening. Max 3 attempts. Output: .voice-phase/05-hook-score.json.

  6. VALIDATE: Call the Skill tool with voice-validator (or run Voice Validation below). Measure metrics against Phase 3 targets. Flag deviations > 1 stddev. Output: .voice-phase/06-validation-report.json.

  7. REFINE: Fix failed metrics. Tighten prose. Verify code examples. Re-validate changed sections. Output: .voice-phase/07-refined-draft.md.

  8. VARIETY-GATE: Sentence length clusters: short (1-7 words) 30-45%, medium (8-20) 35-50%, long (21+) 10-25%. Every paragraph 3 sentences or fewer. At least 1 single-sentence paragraph per 500 words. Variety score (stddev) >= 8.0. Max 3 attempts. Output: .voice-phase/08-variety-score.json.

  9. JOY-CHECK: Call the Skill tool with joy-check. Ensure the article celebrates problem-solving, not grievance. Output: .voice-phase/09-joy-report.json.

  10. ANTI-AI: Run the private de-AI editor skill. Strip generic transitions, hedge stacking, summary conclusions, self-narrating structure. Voice profile overrides anti-AI rules -- if a flagged pattern exists in the voice profile's corpus, preserve it. Output: .voice-phase/10-antiai-report.json.

  11. CLOSE-GATE: Verify closing uses one of 5 modes (Honest Uncertainty, Practical Trailing Observation, Self-Deprecating Admission, Specific Next Step, Just Stops). Must not summarize, callback to opening, or use "In conclusion". Score >= 7. Max 3 attempts. Output: .voice-phase/11-close-score.json.

  12. OUTPUT: Apply front matter, write to content/posts/YYYY-MM-DD-slug.md. Report all gate scores. Write .voice-pipeline-complete marker. Output: final file.

  13. CLEANUP: Report word count, reading time, preview URL. Flag gates that required multiple attempts.


Mode 2: Voice Creation

7-phase pipeline to build a voice profile from writing samples. Each phase has a gate. Report progress with phase banners (load references/cv-phase-banners.md).

Phase 1: COLLECT (Gate: 50+ samples)

Gather 50+ writing samples across contexts and lengths. Mix sources: Reddit, HN, blog, forum, email, chat, social. Do not clean typos -- imperfections ARE the voice. Do not cherry-pick. Save to skills/voice-{name}/references/samples/*.md.

Phase 2: EXTRACT (Gate: profile.json valid, script exit 0)

Run deterministic analysis:

bash
python3 ~/.claude/scripts/voice-analyzer.py analyze \
  --samples skills/voice-{name}/references/samples/*.md \
  --output skills/voice-{name}/profile.json

Add stylometry bands: python3 scripts/voice-stylometry.py band --samples skills/voice-{name}/references/samples/*.md. Merge into profile.json.

Phase 3: PATTERN (Gate: 10+ phrase fingerprints, 3+ thinking patterns, 2/4 architectures)

Identify distinctive patterns from samples + profile.json. Load references/cv-pattern-identification.md for phrase fingerprints, thinking patterns, wabi-sabi markers, and linguistic architectures. Apply triple-validation rubric from references/cv-extraction-validation.md: every pattern must pass cross-domain recurrence, generative power, and distinguishing exclusivity. Verdict: KEEP / FOOTNOTE / DROP.

Phase 4: RULE (Gate: 4+ positive traits, 6+ contrastive aspects, 3+ prohibitions)

Transform KEEP/FOOTNOTE patterns into rules. Load references/cv-voice-rules-template.md. Build: positive identity (with dampening adverbs), contrastive table (This Voice vs Generic AI), hard prohibitions, wabi-sabi rules, anti-essay patterns, architectural patterns.

Phase 5: GENERATE (Gate: SKILL.md 2000+ lines, samples 400+ lines)

Generate the voice skill files. Load references/cv-skill-generation.md. Create skills/voice-{name}/SKILL.md and config.json. Most line count is SAMPLES, not rules (V7-V9 failed with rules-only; V10 passed with 100+ samples).

Phase 6: VALIDATE (Gate: score >= 60, 0 errors)

Generate 3 test pieces (short, medium, long). Run:

bash
python3 ~/.claude/scripts/voice-validator.py validate \
  --content /tmp/voice-sample-{name}-{N}.md \
  --profile skills/voice-{name}/profile.json --voice {name} --format text --verbose
python3 ~/.claude/scripts/voice-validator.py check-banned \
  --content /tmp/voice-sample-{name}-{N}.md --voice {name}

If validation flags natural imperfections as errors, adjust config.json thresholds, not the content. Max 3 iterations.

Show full SKILL.md (528 more words)Show less
Phase 7: ITERATE (Gate: 4/5 authorship match)

Authorship matching: present hold-out samples mixed with generated samples to 5 roasters. Target: 4/5 say SAME AUTHOR. Load references/cv-iteration-guide.md for the full procedure. If failing, add more samples (not more rules). Max 3 iterations.


Mode 3: Voice Validation

Critique-and-rewrite loop for voice fidelity. Max 3 iterations: scan, revise, rescan.

Phase 1: IDENTIFY TARGET

Determine voice profile, mode, and content to validate. Load the target voice's checklist.

Phase 2: SCAN

Step 0: Run deterministic stylometry checks if the voice has a profile.json:

bash
python3 scripts/voice-stylometry.py check \
  --profile skills/voice-{name}/profile.json --draft <content-file>

Checks: burstiness band, punctuation profile, corrective antithesis, temporal openers, uniform paragraph shapes, profile decay.

Step 1: Run negative prompt checklist across all categories: Tone, Structure, Sentences, Language (ban: amazing, terrible, revolutionary, perfect, game-changing, transformative, incredible, outstanding, exceptional, groundbreaking), Emotion, Questions, Metaphors. For 500+ word content, add Narrative category (load references/narrative-patterns.md).

Step 2: Check pass conditions: feels human-written, voice-specific patterns present, could NOT be posted on LinkedIn without edits (for casual voices).

Step 3: Document each violation with: category, quoted text, fix recommendation.

Phase 3: REVISE

Apply the smallest change that resolves each violation. Preserve meaning. Keep substance and arguments intact.

Phase 4: VERIFY

Rescan revised content. If PASS: output with validation report. If FAIL and iteration < 3: return to Phase 3. If FAIL and iteration = 3: output with flagged concerns.


Mode 4: Professional Communication

Transform dense technical communication into structured business formats.

Phase 1: PARSE

Classify input type (technical update, debugging narrative, status report, dependency discussion). Extract ALL propositions: facts, implications, temporal markers, system references, blockers, emotional context. Document implicit context. Count propositions.

Phase 2: STRUCTURE

Categorize propositions: Status, Actions, Impacts, Blockers, Next. Prioritize by business impact: Business Impact > Technical Functionality > Timeline > Resources > Risk.

Phase 3: TRANSFORM

Apply standard template (load references/pc-templates.md for full library):

STATUS: GREEN|YELLOW|RED
KEY POINT: [single most important takeaway]
Summary: [3 bullets: accomplishment/issue + impact]
Technical Details: [2-3 sentences]
Next Steps: [specific actions with verb, scope, owner, timeline]

Tone rules: strip hedging, transform defensive language, preserve urgency markers, keep technical terms intact. Status: GREEN (complete, no follow-up), YELLOW (resolved with follow-up or blocked), RED (active critical issue). Always document reasoning.

Phase 4: VERIFY

Compare output against extracted propositions -- zero information loss. Verify technical accuracy. Confirm status matches severity. Validate action items have (verb, scope, owner, timeline). Check detail level for audience.


Mode 5: Translation

Translate documents using three modes: quick (single-pass), normal (analyze-then-translate), refined (full pipeline with polish). Core principle: rewrite as a skilled native writer, not word-for-word conversion.

Phase 1: DETECT AND PREPARE

Infer mode: "quick/fast/draft" = quick; "professional/polished/refined" = refined; default = normal. Detect source and target languages. Flag documents > 2000 words for chunked parallel translation. Load references/tr-modes.md.

Phase 2: ANALYZE (skip in quick mode)

Identify: language/dialect, register (academic/technical/narrative/marketing/casual/legal), document type, specialized terminology. For technical content, build glossary (load references/tr-glossary-template.md).

Phase 3: TRANSLATE

Translation principles: use idiomatic target-language word order; break long source sentences at natural target-language pauses; render metaphors by intent, not literally; annotate specialized terms on first use; match register from Phase 2; preserve proper nouns and brand names.

For documents > 2000 words: split at heading/paragraph boundaries, build session glossary, dispatch parallel subagent calls per chunk with glossary injected, reassemble, check term consistency.

Phase 4: POLISH (refined mode only)

Scan for register inconsistency. Rewrite literal-sounding constructions. Audit specialized term handling.

Phase 5: DELIVER

Report: source, target, mode, word count, chunks, untranslated terms.

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

Files

SKILL.md and 11 other files (references) in skills/content/writing of notque/vexjoy-agent.

  • SKILL.md
  • references/cv-extraction-validation.md
  • references/cv-iteration-guide.md
  • references/cv-pattern-identification.md
  • references/cv-phase-banners.md
  • references/cv-skill-generation.md
  • references/cv-voice-rules-template.md
  • references/narrative-patterns.md
  • references/pc-examples.md
  • references/pc-templates.md
  • references/tr-glossary-template.md
  • references/tr-modes.md

Open the folder on GitHubat commit 5218674

Compare with similar skills

Writing 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.

Writing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Writing this skillnotque/vexjoy-agent435—~3.4kAutomated safety check: NotesMIT
Translation Diff ExportDevolutions/UniGetUI26k—~1.1kAutomated safety check: PassMIT
Sync Translationssymfony/symfony31k—~1.9kAutomated safety check: PassMIT
Translation Diff ImportDevolutions/UniGetUI26k—~750Automated safety check: PassMIT
Translation Diff TranslateDevolutions/UniGetUI26k—~934Automated safety check: PassMIT
Generate Translationspayloadcms/payload45k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Translation Diff Export

    Devolutions/UniGetUI

    Compares UniGetUI JSON locale files against English, identifies untranslated or source-changed keys, and generates patch, reference, and handoff files for a target language.

    26k GitHub stars~1.1k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Sync Translations

    symfony/symfony

    Synchronize translation catalogs across maintained Symfony branches: find messages that newer branches added to the English catalogs but that are still missing from the oldest maintained branch…

    31k GitHub stars~1.9k tokensUpdated today
    Writing & ContentAuto-check passed
  • Translation Diff Import

    Devolutions/UniGetUI

    Merges translated key-value pairs from a UniGetUI JSON localization patch back into the full language file and validates the merged result.

    26k GitHub stars~750 tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Translation Diff Translate

    Devolutions/UniGetUI

    Translates a sparse UniGetUI JSON language patch, writes completed entries into the working copy, preserves placeholders and terminology, and prepares the patch for merge-back.

    26k GitHub stars~934 tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Generate Translations

    payloadcms/payload

    A skill your agent uses when new translation keys are added to packages to generate new translations strings

    45k GitHub stars~1.1k tokensUpdated today
    Writing & ContentAuto-check passed
  • Drives long-form fiction, scripts, storyboards, interactive films and long-document translation through InkOS, with every change made by a typed action.

    10k GitHub starsUsed in 1 repo~1.1k tokens
    Writing & ContentAuto-check passed

More from notque/vexjoy-agent

All 61 skills in this repo
  • Game Asset Generator

    notque/vexjoy-agent

    Deterministic palette/matrix pixel art (not AI). An agent skill from notque/vexjoy-agent.

    435 GitHub stars~2.3k tokensUpdated 4 days ago
    Auto-check: notes
  • PR Workflow

    notque/vexjoy-agent

    Pull request lifecycle: commit, codex review, sync, review, fix, status, cleanup, and PR mining.

    435 GitHub stars~2.8k tokensUpdated 4 days ago
    Auto-check: notes
  • Architecture Deepening

    notque/vexjoy-agent

    Improve architecture across modules by deepening interfaces.

    435 GitHub stars~3.3k tokensUpdated 4 days ago
    Auto-check: notes
  • Code Quality

    notque/vexjoy-agent

    Code quality: cleanup, linting, formatting, quality gates. An agent skill from notque/vexjoy-agent.

    435 GitHub stars~1.5k tokensUpdated 4 days ago
    Auto-check: notes
  • Codebase Analyzer

    notque/vexjoy-agent

    Statistical rule discovery from Go codebase patterns. An agent skill from notque/vexjoy-agent.

    435 GitHub stars~2k tokensUpdated 4 days ago
    Auto-check: notes
  • Comment Quality

    notque/vexjoy-agent

    Review and fix temporal references in code comments. An agent skill from notque/vexjoy-agent.

    435 GitHub stars~2k tokensUpdated 4 days ago
    Auto-check: notes

Questions about Writing

What does Writing do?

Writing: voice creation and validation, prose editing, anti-AI cleanup, professional communication, translation. Writing is an agent skill from notque/vexjoy-agent. Writing: voice creation and validation, prose editing, anti-AI cleanup, professional communication, translation.

When should I use Writing?

Writing fits situations like: tasks that involve Translation.

How do I install Writing in Claude Code?

Run `npx skills add notque/vexjoy-agent --skill writing -a claude-code`. Or copy the skill folder (skills/content/writing in notque/vexjoy-agent) into .claude/skills/writing in your project. Claude Code loads it when a task matches its description.

How do I install Writing in Codex?

Run `npx skills add notque/vexjoy-agent --skill writing -a codex`. Or copy the skill folder (skills/content/writing in notque/vexjoy-agent) into .agents/skills/writing in your project. Codex loads it when a task matches its description.

Can I use Writing 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 notque/vexjoy-agent --skill writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing, .gemini/skills/writing, .github/skills/writing and .opencode/skills/writing in your project.

What does Writing need to run?

Going by SKILL.md and its folder, Writing needs the command-line tools its instructions call (python3). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Bash, Grep, Glob, Edit, Task, Skill, Agent.

Does Writing 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 Writing 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 Writing use?

Writing 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 Writing use?

About 3.4k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 18k tokens, read only when the agent opens those files.

What are the alternatives to Writing?

Skills that share tags, products or a category with Writing: Translation Diff Export (Devolutions/UniGetUI, 26k stars), Sync Translations (symfony/symfony, 31k stars), Translation Diff Import (Devolutions/UniGetUI, 26k stars) and Translation Diff Translate (Devolutions/UniGetUI, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Writing?

notque (a GitHub user) maintains it in notque/vexjoy-agent, which has 435 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on October 3, 2026.

Source: notque/vexjoy-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.