Skip to content
t-udaPublic

About

Agent skills

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

169 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

skills

This repository is the source of truth for a small set of reusable agent skills.

The default distribution model is conservative:

  • keep each skill under version control in this repository
  • avoid public registries and auto-install workflows by default
  • link only the required skills into a project workspace when needed

Repository layout

skills/
  <skill-name>/
    SKILL.md
scripts/
  install-skill.sh

Each skill must live at skills/<skill-name>/SKILL.md.

Current skills

Planning flow

  • triage: choose the lightest adequate planning route for a development task
  • lite-spec: write a compact execution brief for bounded implementation work
  • metaplan: review and tighten specs, plans, and task breakdowns before autonomous implementation

Source-of-truth review

  • sot-integrity: audit a source-of-truth artifact for authority, evidentiary grounding, trust scope, and conflict with repository reality before implementation or orchestration relies on it

Bibliographic review

  • bib-integrity: verify and repair academic bibliographic records against authoritative sources — work identity, authorship, publication metadata, persistent identifiers, version status, and citation-style representation

Artifact cleanup

  • deslop-history: clean final user-visible artifacts from accepted decisions or issue/PR discussion by removing historical residue and process framing
  • deslop-prose: clean near-final academic or professional prose of hype, decorative structure, excessive paragraph fragmentation, vague metadiscourse, pseudo-technical phrasing and rhetorical overstatement while preserving technical meaning

Writing structure

  • exposition-flow: plan, draft, restructure, compress, or review reader-facing documents and presentations for audience fit and prerequisite order, carrying forward the agreed audience model and communication goal

Orchestration

  • light-orchestration: choose between single-agent execution and a minimal multi-agent split, and produce strictly bounded subtask contracts when a split is justified

Handoff

  • handoff-prompt: generate a compact prompt for the next agent or stage

Teaching and delivery

  • teaching-materials: design and validate educational content and assessment criteria, maintain accepted versions, and coordinate delivery attributes
  • webclass-operations: discover applicable WebClass attributes, map the shared target model to import/UI operations, and verify saved state and delivery
  • human-intervention-management: keep task authority separate from runtime permissions, coordinate necessary human attention, and continue authorized accessible work

These skills compose conditionally through their linked entry points and existing task state. Installing one does not install its companions; load the needed companion from an available source or report the missing capability. Source packaging here does not activate skills in another project.

Notebook review

  • marimo-reactive-review: review an existing marimo notebook for reactive design quality and refactor opportunities

Data inspection

  • headson: preview large JSON, YAML, JSONL/NDJSON, text, source code, multi-file data, and Jupyter notebooks with structure-aware hson previews under explicit budgets

Computational reproducibility

  • computational-reproducibility: keep computational experiments reproducible through explicit preflight checks, manifest expectations, source/artifact separation, fallback policy, and failure semantics

Lean / formalization

  • lean-formalization-discipline: keep Lean / Mathlib proofs sound and axiom-clean while refactoring — no sorry on false statements, honest sorry over hidden axioms, self-contained in the repo, and lake build + #print axioms re-verified every commit

Mathematical writing

  • math-claim-integrity: audit the structural and logical integrity of a mathematics paper — quantifier scope, proof/computation honesty, theorem hierarchy, contribution-list discipline, stale claims, and standing assumptions; target the exact contextual claim, separate identified defects from incomplete verification, and inspect the formal declarations behind machine-checked claims
  • math-notation-consistency: review mathematical documents for undefined or conflicting notation, undeclared aliases, live-scope ambiguity, unrecoverable references, orphaned LaTeX macros, low-value abbreviations, and structural nouns that obscure their contextual role
  • math-proof-exposition: draft or review human-readable proofs so proof modes are announced, introduced objects have a visible purpose, detail follows mathematical difficulty, and compression keeps a sufficient reason
  • formal-proof-exposition: turn formal proofs and formalisation-discovered repairs into human mathematical exposition, recovering objects from representations and preserving genuine repairs
  • math-schematic-figures: plan, draw, revise and review explanatory mathematical figures, including proof-dependency diagrams, preserving mathematical correspondences and requiring independent inspection of the rendered figure in context
  • math-semantic-preservation: review or rewrite mathematical prose against its semantic source to preserve referents, operations, domains, quantifiers, equality, provenance and notation roles, including almost-sure or almost-everywhere claims whose probability context is inherited
  • wabun-math: route Japanese mathematical writing by passage role and terminology task
  • wabun-math-theorem: draft and review Japanese wording in explicitly structured definitions, results, proofs and remarks, including Markdown equivalents
  • wabun-math-style: draft and review narrative Japanese mathematical prose, with shared language rules and default drafting preferences
  • wabun-math-terminology: research meaning and established Japanese usage for every terminology operation, reuse verified evidence, and retain English when no standard Japanese translation is found
  • math-writing-preferences: personal conventions for zero-inclusive natural numbers and zero-based indexing in all languages, automatically applied for a known uda/t-uda user or a target repository owned by t-uda/uda-lab; preserve explicit source conventions and keep preferences distinct from mathematical correctness

The Japanese writing skills share references shipped inside wabun-math-style and use the terminology companion when needed. Install the required companions alongside them, or resolve them from an available skill source; single-skill installation does not install dependencies.

Research review

  • research-significance: assess whether a mathematical or applied-mathematical research direction is locally significant — separating correctness, novelty, and scholarly value — before prose polishing or source-of-truth treatment

Repository guidance

  • growing-agents-md: seed, lint, or update a compact canonical AGENTS.md with deterministic guardrails

Git maintenance

  • git-workspace-cleanup: workspace-level Git cleanup — merged branches, merged worktrees, stale remote-tracking refs, and stale worktree metadata across all repos under the workspace root

External skills

  • external-skill-review: review a candidate external skill against the repo policy, record approved entries in a project-local catalog, and recommend install commands

Dev containers

  • devcontainer-cli: review, validate, and troubleshoot Dev Container setup with explicit CLI-first guidance

Shell scripting

  • shell-script-engineering: create, edit, or review non-trivial Bash/sh where correctness depends on execution context, permissions, filesystem mutation, argument parsing, idempotency, or CI/container behaviour

Delivery workflow

  • github-driven-workflow: deliver an authorised GitHub issue through a branch, validation, independent review and a gated PR merge; distinguish review evidence from resolved findings and merge authority, and continue autonomously within the existing delegation
  • github-loop-engineering: run bounded, supervised-autonomous repository work through a dynamic authorized GitHub Issue queue, per-Issue delivery gates, independent quality review, and repository-hygiene constraints
  • github-project-board-maintenance: rate-limit-aware GitHub Projects v2 board maintenance — REST-first candidate discovery, single GraphQL snapshot, mechanical status-update planning, and guarded apply

Randomness

  • randomness: prefer a bundled PRNG script for random selection; fall back to a String Seed prompt pattern only for low-stakes or creative-diversity use

Coding-agent orchestration

  • claude-code-advanced-orchestration: operational guidance for delegating implementation work to Claude Code as a worker behind a coordinator agent (session identity, permission strategy, worktree/tmux patterns, dynamic agents, effort selection, bare-mode auth, MCP trust, remote-control caveats)

Text linting

  • textlint-cli: invoke textlint correctly from the CLI in repositories with existing configuration — detection, repo-local invocation, fix mode, diagnostics, CI-oriented formats, and MCP mode

Naming guidance

Prefer short, command-friendly names.

Use names that:

  • are easy to invoke directly as slash-style commands
  • distinguish categories without excessive prefixes
  • describe the skill's role in a few syllables
  • avoid avoidable collisions with common built-in commands such as /plan

Tool compatibility

This repository targets multiple coding agents, but each tool discovers reusable guidance differently:

  • Claude Code: project-local skills in .claude/skills/
  • Codex: project-local skills in .agents/skills/
  • GitHub Copilot CLI: project-local skills in .github/skills/ or .claude/skills/
  • Gemini CLI: project-local skills in .agents/skills/

Installation model

The installer script links skills from this repository into a target workspace by default. It does not depend on a remote marketplace or registry. It runs with python3 when available and falls back to uv. Use --copy when a workspace needs its own editable copy. Use --force to replace an existing real directory or file. For external skills installed directly from upstream repositories, see docs/external-skills.md.

Supported targets:

  • claude: install to .claude/skills/
  • codex: install to .agents/skills/
  • copilot: install to .github/skills/
  • gemini: install to .agents/skills/
  • all: install to all supported agent locations

Examples:

./scripts/install-skill.sh all all
./scripts/install-skill.sh triage codex .
./scripts/install-skill.sh lite-spec copilot /path/to/workspace
./scripts/install-skill.sh metaplan gemini /path/to/workspace
./scripts/install-skill.sh handoff-prompt all /path/to/workspace
./scripts/install-skill.sh triage codex /path/to/workspace --copy
./scripts/install-skill.sh triage codex /path/to/workspace --force

APM installation

This repository is compatible with APM (Agent Package Manager).

Install individual skills via subpath:

apm install t-uda/skills/skills/triage
apm install t-uda/skills/skills/metaplan
apm install t-uda/skills/skills/lite-spec

Install with pinned commit:

apm install t-uda/skills/skills/triage#abc1234

APM automatically deploys skills to detected target directories (.github/skills/, .claude/skills/, .agents/skills/, etc.).

The manual installer script remains available for environments where APM is not installed.

Install-first, compile-minimal

This repository favours native install over compiled instruction files:

  • apm install is the preferred path. Skills land directly in each tool's native directory.
  • apm compile output (AGENTS.md, CLAUDE.md) is treated as a compatibility layer only.
  • Compiled artifacts in this repo stay compact: durable policy, minimal guardrails, and pointers. Procedures live in skill files, not in compiled documents.

Current APM scope

Phase 1 covers skills only. Prompts, agents, instructions, hooks, and MCP are not distributed from this repository yet. See docs/apm-consumption.md for supported primitives, target-directory mapping per tool, and subpath install patterns.

Project instruction files

These are separate from skills, but they affect project-local behaviour:

  • GitHub Copilot supports AGENTS.md, GEMINI.md, and .github/copilot-instructions.md
  • Gemini CLI loads hierarchical GEMINI.md files and can be configured to accept other context filenames

The installer in this repository manages skills only. It does not generate repository-wide instruction files such as AGENTS.md or .github/copilot-instructions.md.

Notes

  • Keep repository files and skill artifacts in English.
  • Keep skills narrow, explicit, and easy for agents to apply.
  • Prefer project-local installation unless there is a clear reason to install globally.

About

Agent skills

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages