Andrew J Schmitt
Community@schmitthub
Andrew J Schmitt maintains Claude Code skills for developing clawker, a Go CLI with testing, monitoring, firewall, and TUI wizard subsystems.
Agent Skills by Andrew J Schmitt
Showing 12 vetted skills indexed across 1 GitHub repositories.
schmitthubstore-editor
Build interactive TUI editors for storage.Store configuration schemas in Go.
schmitthubdev-checks
Runs build, test, lint, and documentation checks for the clawker Go repository.
schmitthubwizard-commands
Implement interactive prompts and multi-step BubbleTea wizards for clawker CLI commands.
schmitthubaudit-memory
Audits agent instruction files, memory stores, and project docs for staleness, symbol errors, and context budget overruns.
schmitthubagent-files
Maintains shared AGENTS.md instructions, skills, and hooks for Claude Code and Codex.
schmitthubcli-output
Implements stdout/stderr stream conventions, tables, format flags, and TUI progress display for clawker CLI commands.
schmitthubinitiative
Plans and executes multi-task development initiatives with shared memory and per-task handoffs.
schmitthubwriting-tests
Guides writing Go tests in clawker using fakes, moq mocks, command test tiers, and e2e harnesses.
schmitthubmonitoring-checks
Validates changes to the OpenTelemetry, Prometheus, and OpenSearch monitoring stack.
schmitthubfirewall-uat
Runs live egress probes inside a clawker container to verify firewall enforcement behavior.
schmitthubtest-hunter
Audits new or changed Go tests to flag wasteful, tautological, and redundant test cases.
schmitthubcode-review
Reviews pull request diffs against repository-specific lint, security, and versioning rules.
Frequently Asked Questions About Andrew J Schmitt
FAQPage SchemaWhat tasks can I accomplish with schmitthub's skills?▼
These skills cover clawker development: writing and auditing Go tests, building CLI output with tables and format flags, adding wizard TUI prompts, editing store adapters, verifying OpenTelemetry and Prometheus monitoring, running firewall egress UAT probes, and reviewing pull requests.
Who are these skills designed for?▼
Engineers contributing to the clawker project, particularly Go developers working on its CLI, test harnesses, monitoring stack, and firewall controlplane. They also serve maintainers auditing agent instruction files like AGENTS.md, CLAUDE.md, and Serena memories for stale content.
How do these skills work in practice?▼
Each skill is invoked contextually during clawker development: dev-checks handles builds, dependency pins, and doc regeneration; writing-tests and test-hunter govern Go test creation and quality audits; firewall-uat runs live egress probes after firewall rule changes; code-review handles pull request reviews.
What prerequisites or dependencies do these skills require?▼
Skills assume access to the clawker repository and its Go toolchain, including moq mocks, the e2e harness, and golden files. Monitoring work requires the OpenTelemetry collector, Prometheus, and OpenSearch stack; firewall UAT requires running inside a clawker container.
Are there usage restrictions on any skills?▼
Yes. audit-memory has disable-model-invocation enabled and runs only when the user explicitly requests an audit of agent instructions, memory files, and project docs. The initiative skill is reserved for multi-task work needing handoffs across conversations, not routine single-task changes.