Profile My skills Saved My plugins Edit profile Submit a skill

← all publishers

minpeter

@minpeter source repo

5 published skills

  1. ▌
    Tool Schema Design · minpeter bundle
    Designs JSON Schemas for LLM tool/function calling that survive across providers. Use when writing tool definitions, function-calling `parameters`, an MCP tool `inputSchema`, or zod/Pydantic tool schemas; when deciding between anyOf/oneOf/allOf; when choosing format/enum/description usage; or when one schema must run on several providers or strict modes (OpenAI, Anthropic, Gemini, Vertex, Bedrock, Cohere, xAI, DeepSeek, Fireworks, FriendliAI, vLLM/SGLang, and more). Covers the canonical-schema + adapter architecture, the hard rules (root object, no oneOf/allOf, nested anyOf allowed, no $ref/default/constraint keywords in the canonical schema), strict-mode transforms, the authoring guide for names, descriptions, and errors (what to write, what style, how long), and tool-design practices beyond the schema (naming, tool count, consolidation, output and error design, evals).
    0 installs
  2. ▌
    Typescript Package · minpeter bundle
    minpeter's house style for building and reviewing TypeScript packages and monorepos. The locked stack: pnpm (latest) + Turborepo + Changesets + Biome via the ultracite preset with ZERO ignores/overrides/suppressions + tsdown for builds + Vitest, with `tsc --noEmit` for type-checking, the namespaced source-condition for zero-build internal deps, and MANDATORY npm OIDC trusted publishing (no NPM_TOKEN). Use this when scaffolding a new TS library or monorepo, adding a workspace package, choosing build/lint/publish tooling, or reviewing an existing package.json / tsconfig / biome.jsonc / turbo.json / CI for consistency with this style. Copy-paste config lives in references/templates.md; the source-condition deep-dive + external verdict in references/source-condition.md; the OIDC publishing guide in references/publishing-oidc.md.
    0 installs
  3. ▌
    Hermes Agent Consult · minpeter bundle
    Consult the local `hermes` agent as the long-term-memory oracle for minpeter's machines, from inside another coding agent (pi, codex, senpi, Kiro, Claude Code). Use it whenever a task needs context the repo does not contain — infrastructure layout, hostnames/ports/routing, why a past decision was made, prior incidents, cross-repo conventions, deploy/ops procedure — and the instinct is to ask the user: run `hermes -z "<query>"` FIRST, then ask the user only what hermes could not answer. Also use it after an infra change or a long-lived decision, to write that fact back into hermes memory (`-t memory`), and for a second-opinion review of a diff or plan from an agent that has the operational history. Covers query construction, why a failed run can still look like an answer (`--usage-file`), auto-approved tools, and what must never be sent to a hosted model. Query templates: references/queries.md. CLI flags, memory layout, troubleshooting: references/cli.md.
    0 installs
  4. ▌
    Capturing UI Screenshots · minpeter
    Captures reproducible evidence screenshots and browser states from web apps in Amp orbs with Playwright, mock authentication, mocked APIs, supervised preview services, and visual verification. Use when a UI change needs review PNGs, browser-state evidence, or reliable Radix Select and AlertDialog captures; especially when portal locators detach, overlays animate, or screenshots must come from an existing single-worker E2E flow.
    0 installs
  5. ▌
    Minpeter Skills Maintainer · minpeter bundle
    Maintains the minpeter/minpeter-skills repository — minpeter's collection of Agent Skills in the open SKILL.md format. Use this when adding a new skill there, editing or refining one, splitting an oversized SKILL.md into references/, renaming or removing a skill, or fixing drift between SKILL.md frontmatter, README.md's index table, and skills.sh.json groupings. Also use it when the user says "add a skill", "update the skills repo", or "write a skill for X". Covers the mandatory workflow (throwaway /tmp clone → branch → PR → reinstall locally after merge; never edit a checkout in place, never commit to main), `npx skills init`, frontmatter rules including the 1024-char description limit, the three files that must stay in sync, and the pre-commit verification pass. The repo is PUBLIC, so it enforces the no-secrets / no-PII rule: no tokens, credentials, private hostnames, internal URLs, or machine-local paths. Authoring: references/authoring.md. Runbook: references/maintenance.md.
    0 installs