> read-repo-rules
Read specified repo rule files (AGENTS.md, docs/REPO_STYLE.md, docs/PYTHON_STYLE.md, docs/CHANGELOG.md) and return one-sentence summaries in a strict four-line format, including missing-file handling and no recursive listings. For docs/CHANGELOG.md, summarize only the latest dated entry instead of the full file. Use when a prompt asks for structured summaries of repo instruction files with exact output lines or similar constraints.
curl "https://skillshub.wtf/vosslab/vosslab-skills/read-repo-rules?format=md"Read Repo Rules
Overview
Provide strict, one-sentence summaries of key repo instruction files, obeying exact output formatting and missing-file stop conditions.
Workflow
- Verify each provided file path exists (use
ls <paths>ortest -f, no recursive listings). If any missing, outputMISSING: <path>and stop. - Read AGENTS.md, docs/REPO_STYLE.md, and docs/PYTHON_STYLE.md normally (use
sed -n "1,200p"or similar). - For docs/CHANGELOG.md, identify the latest dated entry and read only that entry section (from its heading to the line before the next dated heading, or end of file).
- Produce exactly one sentence per file that states the high-level purpose and what it specifies for an AI agent to do.
- Output lines in the exact order and prefix required by the prompt (for example
AGENTS: ...,REPO_STYLE: ...,PYTHON_STYLE: ...,CHANGELOG: ...). - If the prompt says output exactly these lines or otherwise forbids extra text, do not add anything else.
- If the prompt allows extra text, append the follow-up question: do you (the agent) now know how to run code? is there a source_me.sh file or similar
- Never use
ls -Ror recursive listings; only list the explicit paths provided.
> related_skills --same-repo
> webwork-writer
Create, edit, and lint WeBWorK PG/PGML questions following docs/webwork guidance, HTML whitelist constraints, and renderer-based lint checks. Use for tasks like authoring new PGML problems, adjusting randomization or grading, fixing PGML rendering issues, and running renderer API linting.
> unit-test-starter
Generate thorough Python 3 pytest unit tests across a repo by scanning every *.py file and each function, writing one test module per source file while skipping IO/network behavior and documenting gaps.
> skill-writing-guide
Guide for authoring Agent Skills (SKILL.md). Covers the open standard format, required frontmatter, directory layout, progressive disclosure, description writing, and best practices. Use when creating a new skill, improving an existing skill, or learning how skills work.
> readme-fix
Standardize README.md to match repo conventions. Brief purpose, quick start, and links to docs/. Keep content verifiable, concise, and ASCII. Use when README.md drifted or is missing key pointers.