api/git
67 skills1.8k installsGitHub
Install
npx skills add https://github.com/api/gitSkills in this repo
1Vip Test Planvip-test-plan is a lightly documented agent skill from the api/git skills.sh source, intended to help solo and indie builders think in terms of VIP or highest-risk test coverage before they ship API or repository changes. Prism lists it with minimal SKILL.md body, so you should treat the install as a hook to pull the full skill from the upstream git repository and verify commands, outputs, and gates locally. When populated, skills in this niche typically produce ordered test scenarios, smoke versus regression splits, and acceptance criteria your coding agent can execute or track. Use it when you are past prototype and need a written plan the agent can follow during ship-phase testing rather than ad-hoc "click around" validation. Because public metadata is sparse, review the Security Audits panel on this Prism page and read the source skill file after install before granting shell or network permissions.485installs2Auto DeployAuto-deploy is a narrowly scoped agent skill from the api/git source family aimed at solo builders who want deployment to happen automatically once code lands in git. Public listing metadata is minimal, so you should treat the skill as a deploy-oriented procedural template: connect repository events to a hosting platform, define build steps, and promote artifacts without a manual runbook each time. It suits SaaS APIs, static sites, and small services where the bottleneck is repeating the same deploy commands rather than designing architecture. Expect the agent to suggest standard CI/CD patterns—branch triggers, environment secrets, rollback awareness—even if your SKILL.md is thin on first install. Verify which cloud or PaaS the skill assumes in your fork before trusting production pushes. Prism catalogs it under Ship because it is about getting safe, repeatable releases out the door, not ideation or growth analytics.421installs3Music ConfigMusic-config appears on Prism as a thin skills.sh catalog record sourced from api/git, with almost no procedural SKILL.md content in the ingested readme. Solo builders might still install it when a workflow or marketplace pointer expects that exact slug for music-related application settings, but Prism cannot summarize steps, tools, or outputs from the stub alone. Treat this page as a discovery anchor: verify the cloned skill repository for real instructions before relying on it in production. Until fuller docs land, prefer skills with explicit configuration checklists if you are shipping audio features, streaming integrations, or player presets. Revisit tagging once the upstream package publishes invoke triggers and deliverables.412installs4Music AuthMusic-auth is a thin catalog entry from the api/git source with almost no embedded SKILL.md on Prism, so treat it as a placeholder for music-service authentication work during Build. Solo builders searching for OAuth or token flows for streaming APIs may install it to pull procedural guidance from the upstream repo. Because installs and documentation are sparse, read the actual skill files after install and confirm scopes, redirect URLs, and secret handling yourself. Prism tags it under backend integrations until richer readme content is ingested.409installs5Generate Design DocGenerate-design-doc is a lightweight agent skill from the api/git source on skills.sh, aimed at solo and indie builders who need a written design artifact before or during implementation. Catalog metadata describes it as a ranked generate-design-doc entry with minimal public SKILL.md body in Prism’s ingest, so tags lean on the slug semantics: turning ambiguous requirements into a design document an agent can follow. Use it when you have a feature or integration in mind but lack a single source of truth for scope, interfaces, and constraints. It pairs naturally with validation scoping and build-phase documentation work rather than replacing security review or deployment automation. Treat install counts and momentum as whatever skills.sh reports on the detail page; do not assume enterprise governance features that are not documented in the stub readme.2installs6Vip Arthas AgentVip-arthas-agent is a lightly documented entry in the Prism catalog whose name and source imply an agent skill for Alibaba Arthas-style Java virtual machine diagnostics—typical for tracing slow APIs, inspecting classes, and narrowing production-only defects on JVM backends. Prism’s ingested readme does not expose full procedural steps, so solo builders should install only after reading the upstream repository and any Security Audits on this page. The reasonable use case is Operate-phase incident response when you already run Java services and want conversational guidance to attach diagnostics safely. Confidence is moderate because marketing metadata is sparse compared with fully authored SKILL.md files. If you are not on the JVM stack, skip this skill in favor of language-native observability tooling.2installs7Vip Test Bindvip-test-bind is a thin entry from the api/git skills.sh source with only ingest metadata in the published readme—install counts, slug, and URL—rather than procedural guidance. Solo builders might encounter it while browsing Git-backed API skills or when Prism tests binding between catalog IDs and remote repos. Without invokeWhen text or steps, it is not a turnkey marketing or planning skill; assume it exists to exercise VIP/test binding paths in tooling or CI. Use it only if your workflow explicitly references api/git/vip-test-bind; otherwise prefer skills with complete SKILL.md instructions. Confidence in journey placement is limited to the name and source repo theme (API + Git integration).2installs8Agent Browseragent-browser is an agent skill distributed through the skills.sh api/git channel, intended to wire browser interaction into coding agents so solo builders can drive real pages while implementing features, chasing regressions, or sanity-checking flows. Prism surfaces it under Build agent-tooling because the payoff is tooling: your agent can operate like a developer with a browser open, not just read source files. Catalog ingest for this entry contained minimal metadata (install counts and rank) without SKILL.md procedures, so treat modes, auth handling, and sandbox rules as something you must read from the upstream package before relying on it in Ship or Launch checks. Install when you are building web or hybrid products and want repeatable browser leverage from Claude Code, Cursor, or Codex rather than one-off Playwright snippets in chat.1installs9Auto Submitauto-submit is a minimally documented agent skill listed on Prism from the api/git source. Public catalog metadata exposes rank and install signals but not a full SKILL.md body on this page, so treat it as a git-oriented automation hook whose exact commands, guards, and remotes you must confirm after install. Solo builders typically look for skills like this when they want the agent to complete a submit or push step after reviews pass—reducing copy-paste in Claude Code, Cursor, or Codex sessions. Because documentation is thin here, pair installation with a quick read of the skill files in your environment, define branch protections, and never grant broader git permissions than your repo policy allows. Prism tags reflect inferred git automation intent until richer README content is ingested.1installs10Ci Fix Skillci-fix-skill is a lightly documented agent skill from the api/git source on skills.sh, intended to help solo and indie builders recover when continuous integration breaks. Public catalog metadata does not include a full SKILL.md playbook, so you should treat installs and rank as signals only and inspect the skill package in your repo before trusting automated fixes. The name and source strongly imply Git-provider CI repair—interpreting workflow output, adjusting workflow definitions or related project files, and validating that pipelines pass again. That maps cleanly to the Ship phase for builders who ship through pull requests and automated checks rather than manual deploys alone. Use it when a push or PR suddenly fails checks and you want procedural guidance instead of open-ended chat. Because documentation is thin, combine it with your own review of destructive commands and secret handling; Prism’s on-page security audits are the authoritative safety reference, not inferred pass rates from this stub.1installs11Ci Npe Fixci-npe-fix is a narrowly scoped agent skill published under api/git for builders who hit null-pointer exceptions during continuous integration tied to git or API workflows. Public listing metadata is sparse—there is no rich SKILL.md in the catalog snapshot—so treat it as a specialized CI remediation helper rather than a full methodology. Solo maintainers shipping small API services or git-backed automation often waste hours replaying failed jobs without a structured fix pattern; this skill exists to shorten that loop when the failure mode is an NPE in the pipeline context. Use it in the Ship phase when merges fail on CI, not as a substitute for local unit tests or security review. Because documentation is thin, review the skill package and any Security Audits panel on Prism before granting shell or network access in production repos.1installs12Claude Code Whats Newclaude-code-whats-new is a slim Prism-listed skill from api/git aimed at solo builders who depend on Claude Code as their primary agent shell. The public readme is mostly catalog metadata rather than a long procedural guide, so treat it as a pointer skill: invoke it when you want your agent to reason about recent Claude Code capabilities, breaking changes, or ecosystem moves before you refactor keybindings, MCP wiring, or project-level settings. It sits in Build under agent-tooling because that's where you tune how code gets written, but the same awareness matters when you Ship (new review hooks), Launch (shared demo setups), or Operate (logging and sandbox changes). Without a dense local checklist, pair this skill with official Anthropic release notes and your own SECURITY review. Prism stores installs and audits separately—do not infer safety from the skill name alone.1installs13Code Review TrackerCode Review Tracker is a slim agent skill from the api/git catalog entry on skills.sh, aimed at developers who want pull-request review state visible without building a custom dashboard. Prism lists it for solo and indie builders who treat review as a Ship gate: knowing which PRs lack a second look, which comments block merge, and whether review rot is about to slip a release. Public metadata is sparse compared to full SKILL.md packages, so treat this skill as a naming and intent anchor—install and inspect the upstream skill bundle for exact commands, API scopes, and repository integration steps. It complements heavier code-review skills that write findings; this one emphasizes tracking who reviewed what and what is still open. Use when you are batching merges, running agent review on a branch, or cleaning a stale PR queue before a tagged release.1installs14Create Jibi IssueCreate-jibi-issue is a narrow agent integration skill sourced from the api/git catalog entry on skills.sh. It exists so developers using Claude Code, Cursor, Codex, or similar agents can file a Jibi issue as a structured work item while building, instead of manually switching to another app to log bugs or tasks. Prism lists it under Build and PM because it supports traceability during implementation rather than marketing or growth work. Public readme metadata is thin—rank and install fields come from the skills API and should be read on the Prism detail page, not inferred here—so treat the skill as a git and issue-tracker bridge whose exact API calls and auth requirements live in the full skill package. Best when you already use Jibi (or the referenced git API flow) and want repeatable issue creation prompts in agent sessions.1installs15Create Overmind Taskcreate-overmind-task is a thin integration skill from the api/git catalog that lets coding agents open or record work in Overmind instead of copying titles and descriptions by hand. Solo builders shipping with Claude Code, Cursor, or Codex often lose traceability when the agent fixes something but no ticket exists; this skill closes that gap by standardizing how tasks get created from the agent context. Prism lists it under Build/pm because its job is operational project hygiene during implementation, not ideation research or launch SEO. Public metadata on skills.sh is minimal, so treat install instructions and required credentials as defined in the full SKILL.md in the upstream repository. Use it when you already run Overmind for task management and want the agent to file structured work items as part of a commit or feature request flow.1installs16Cs Api Skill Generatorcs-api-skill-generator is a thin catalog entry from the skills.sh api/git source aimed at builders who maintain Claude Code, Cursor, or Codex skill packs. Public metadata positions it as a generator-style skill for API- and Git-related agent capabilities rather than a single integration task. Install counts and rank on skills.sh are the main signals available in the ingested readme; treat the on-disk SKILL.md in your fork as the source of truth before relying on behavior. Solo and indie builders typically reach for this kind of package when they want a repeatable pattern for authoring skills that talk to repositories, remotes, or HTTP APIs. Use it during the build phase while expanding agent-tooling, after you already know which API or git workflow you are encoding. It is not a substitute for security review, MCP servers, or hand-written domain logic when production behavior must be explicit.1installs17Douyin Crawlerdouyin-crawler is a lightly documented agent skill aimed at automating collection of Douyin short-video platform data for indie builders who work in Chinese social distribution or competitive content research. It ships through the skills.sh api/git channel with minimal public SKILL.md detail, so you should treat it as an integration stub you extend inside your repo rather than a full managed crawler service. Solo operators typically install it when they already run agent workflows for growth or content and need repeatable fetches instead of copying links by hand. Expect to wire credentials, rate limits, and compliance yourself; the skill name signals domain intent more than a polished end-to-end playbook. Use it when Douyin is a first-class channel for your product narrative and you want procedural hooks your coding agent can invoke during research or lifecycle content passes.1installs18Drawio Architectdrawio-architect is an agent skill aimed at helping you produce architecture-oriented diagrams compatible with the draw.io ecosystem. Solo and indie builders often skip formal diagrams until something breaks; this skill is meant to slot into agent sessions when you want boxes, boundaries, and data flows written down in a standard visual format. Without a full public SKILL.md in the catalog excerpt, treat it as a documentation-oriented capability you invoke when planning service boundaries, integration points, or deployment topology. Pair it with your repo’s existing docs folder so diagrams stay versioned next to code. Review the skill source on skills.sh or the originating git repo for concrete invocation steps, templates, and any hard requirements about file formats or export paths before making it part of a recurring workflow.1installs19Emergency CallEmergency call is an agent skill entry sourced from api/git on skills.sh with almost no procedural body in the Prism ingest payload, so solo builders should treat it as a placeholder name for incident or on-call assistance until the upstream repository documents triggers and outputs. Catalog placement defaults to Operate errors because emergency-call conventions usually mean paging, severity classification, comms templates, and rollback hints when production breaks. Without a full SKILL.md in the feed, the skill cannot be confidently ranked as workflow versus integration; agents may still help you draft runbooks if you invoke by name and pair with your own paging tool docs. Confidence stays moderate because rank and single-install signals suggest early or niche adoption. Prefer verified incident skills with explicit checklists before betting a live outage on this package alone, and re-tag after upstream publishes steps, permissions, and required integrations.1installs20Evolve Skillevolve-skill is an agent skill distributed from the api/git well-known source on skills.sh, aimed at solo builders who maintain their own SKILL.md libraries instead of only consuming static marketplace snapshots. Public metadata is sparse, but the name and placement imply a meta workflow: revise skill instructions, triggers, and handoffs as your product and agent stack mature. Use it when you already version skills beside application code and want a procedural hook for structured evolution rather than one-off chat edits. It suits Claude Code, Cursor, and Codex users who install from skills.sh git routes and care about repeatable skill upgrades across Validate, Build, and Operate cycles. Treat documentation in your fork as authoritative for exact steps, gates, and outputs. Combine with brainstorming or writing-plans when evolution follows a spec change, and with testing skills before you promote evolved packages to production agents.1installs21Excel Readerexcel-reader is a lightly documented Prism-listed skill sourced from api/git, positioned for agents that need to read Excel workbooks as part of a solo builder’s product or internal tooling. Catalog metadata confirms the skill identity and install channel rather than a long SKILL.md narrative, so you should treat it as a focused capability hook: invoke when your task is to load .xlsx or legacy Excel data into code, summaries, or downstream APIs. It fits Build-phase work where spreadsheets remain the source of truth for pricing, inventory, or operations exports. Pair the skill with clear file paths, sheet names, and output schemas in your prompt so the agent does not guess structure. Confidence is moderate because public readme content is minimal; verify behavior in your environment before production pipelines depend on it.1installs22File Uploaderfile-uploader is a thin agent skill sourced from api/git on skills.sh for uploading files via that API. Solo and indie builders who automate releases, asset sync, or agent-driven repository updates install it when their workflow already shells out to skills.sh capabilities and needs a named upload step instead of bespoke curl scripts. Prism lists it under build integrations because it does not prescribe research, validation experiments, or launch distribution—it assumes you have a repo, a target path, and permission to push bytes. Documentation in the catalog is sparse relative to full SKILL.md guides, so treat the skill as a hook to discover the api/git upload contract and validate behavior in your own environment before production use. It complements broader git and DevOps skills rather than replacing hosting, CI, or review workflows.1installs23Generate Review Record DocThis tool generates structured documentation and review records for code changes, capturing review feedback, decisions, and approvals in a standardized format. Solo builders use it to maintain clear audit trails of their code quality processes and document why changes were approved or modified. It matters because comprehensive review records support compliance requirements, help teams learn from past reviews, and create accountability for code quality decisions.1installs24High Sql Code Analyzerhigh-sql-code-analyzer appears on Prism via the skills.sh api/git feed with minimal public README beyond listing metadata, so builders should treat it as a database-oriented analysis skill aimed at SQL-heavy SaaS and API backends. The intended use is likely pre-ship review: scanning SQL strings, migration files, or stored procedures for complexity, anti-patterns, or risk before merge. Solo founders shipping Postgres or MySQL-backed products benefit when agents otherwise skip SQL in generic code review. Because procedural detail is not ingested here, install the skill and read its local SKILL.md for triggers, severity buckets, and output format. Position it in Ship review alongside ORM migrations and data access layers; skip it if your stack has no SQL surface. Confidence is moderate until full skill text is available in the catalog.1installs25Java Snapshot Checkjava-snapshot-check is a narrow agent skill from the api/git ecosystem for solo builders shipping JVM backends who rely on snapshot files to lock dependency graphs or build outputs. Public listing metadata is minimal, but the name and placement imply a checker you invoke in Ship-phase automation: compare the current Maven or Gradle resolution (or related snapshot artifact) against the committed baseline and stop the pipeline when versions or hashes drift. It suits indie teams that want agents to run the same guardrail locally and in CI without writing custom scripts each time. Pair it with your existing test stage rather than treating it as a codegen or deployment skill.1installs26Knowledge To VaultKnowledge to Vault is a lightly documented api/git agent skill aimed at solo builders who want conversational or repo knowledge consolidated into a vault-shaped store for long-term reuse. Prism lists minimal SKILL.md body for this entry, so treat the name and catalog placement as the primary signal: it targets documentation hygiene and persistent second brains rather than shipping features or running infra. Invoke it when you are mid-build or wrapping a spike and need to promote decisions, snippets, and research into structured notes your agent can cite on the next session. Because public README content is thin, combine this skill with your own vault conventions (folders, tags, frontmatter) and verify behavior in your agent after install.1installs27Know Score Preview`know-score-preview` is a minimal well-known entry sourced from the skills.sh `api/git` channel, intended for agents and solo builders who discover tools through API snapshots rather than browsing alone. Prism surfaces it for the Idea phase when you want a preview-oriented handle on catalog scoring or ranking context before you clone a repo or add a skill to Claude Code, Cursor, or Codex. Public metadata in the stub shows very low install volume, which makes it a niche integration for custom discovery automations—not a full marketing or analytics suite. Treat it as a programmatic peek tied to skills.sh identifiers; validate behavior against live API responses and your agent’s network policy, and use richer skills once you move from Discover into Validate or Build.1installs28Maven Conflict ResolverMaven Conflict Resolver is an agent skill aimed at solo and indie builders maintaining Java or JVM backends who hit dependency hell in pom.xml files. When builds fail with version convergence errors, duplicate classes, or mysterious transitive pulls, the skill guides structured diagnosis and remediation so you can pick consistent artifact versions without guessing. It sits in the Build phase on the backend shelf because that is where dependency graphs are defined and where failures surface first, though the same fixes often unblock Ship-phase CI pipelines. Prism lists it for builders using Claude Code, Cursor, or Codex on Maven projects who want procedural help instead of ad-hoc Stack Overflow threads. Catalog metadata is thin on api/git, so treat outputs as suggestions you verify with mvn dependency:tree and your team policies.1installs29Md Doc Uploadermd-doc-uploader is a lightly documented api/git skill on Prism whose name implies pushing markdown files into a documentation or repository-backed upload flow. Solo builders who automate docs from their agent stack might install it to avoid manual copy-paste into a docs site or git path, but the public readme here only exposes catalog metadata—not step-by-step triggers or API shapes. Treat it as a documentation integration candidate: confirm what endpoint or git remote it targets, what auth it needs, and whether it validates front matter before you rely on it in CI. Confidence stays moderate until full SKILL.md body is available in your environment.1installs30Mlog Querymlog-query is a thin skills.sh entry from the api/git source aimed at agents that need log-oriented queries tied to git-backed workflows. Public listing metadata is minimal, so treat it as a specialized git/API companion skill you install when your stack already pulls skills from api/git and you want a named capability for log lookup instead of improvising shell one-liners. Solo builders shipping CLI tools or APIs who version everything in git may use it during incident triage or when an agent needs structured access to log-related operations through the same channel as other api/git skills. Confirm behavior in the installed SKILL.md before relying on it in automation.1installs31Multi Person TaskMulti-person-task is a lightly documented agent skill from the api/git lineage on skills.sh, aimed at builders who need clearer ways to split and follow through on work when a repo is no longer a one-person sandbox. The catalog entry does not ship a long procedural checklist like richer methodology skills; instead it signals intent around shared ownership, task boundaries, and git-backed collaboration that indie teams hit as soon as they add a second contributor or run multiple agent sessions on the same codebase. Install it when you want a named capability hook for PM-style coordination rather than improvising assignments in chat. Because documentation is minimal, combine it with your own task list format, branch strategy, and review gates. Prism lists it for discoverability alongside other git- and workflow-adjacent skills; verify behavior in the cloned skill package before relying on it in production team rituals.1installs32Music Test PlanMusic Test Plan is a lightly documented agent skill surfaced on skills.sh under api/git with minimal README beyond catalog metadata. Prism tags it conservatively for solo builders who discover it by name and need a ship-phase testing anchor for music apps, audio pipelines, or music-education products. Without a full SKILL.md body in the ingest snapshot, treat the skill as a prompt to produce or extend formal test plans—scopes, environments, regression suites, and release criteria—rather than a guaranteed turnkey integration. Install only after cloning or inspecting the source repository for the actual procedures, templates, and gates. Confidence is reduced because marketing copy and step lists are not present in the indexed excerpt; the value proposition is inferred from the skill name and Testing & QA placement. Re-tag after the full skill file is available.1installs33Nss Rpc Qps Scannss-rpc-qps-scan is a performance monitoring tool that measures query-per-second (QPS) throughput for RPC endpoints and backend APIs. Solo builders use it to understand how many requests their service can handle and detect performance degradation in production. This matters for maintaining service reliability, capacity planning, and ensuring users experience responsive APIs.1installs34Nss Server Qps Scannss-server-qps-scan is a performance monitoring tool that measures queries-per-second (QPS) throughput for backend servers and APIs. A solo builder uses it during production operations to identify capacity limits, detect performance degradation, and optimize server resources. This matters because understanding QPS helps prevent overload scenarios and informs scaling decisions before systems fail.1installs35Owl2 Ddb Queryowl2-ddb-query is a lightly documented skills.sh entry sourced from api/git whose slug and name point at DynamoDB querying—likely an owl2 or AWS DDB helper for coding agents. Prism’s ingest captured ranking and install metadata but not the full SKILL.md body, so solo builders should treat this page as a discovery stub and pull the complete skill from the publisher before relying on query semantics, IAM assumptions, or table schemas. For a typical indie SaaS or API on AWS, the natural journey moment is Build while wiring persistence: agents need repeatable, safe patterns for key-condition expressions, batch reads, or operational queries instead of one-off console copying. Tag confidence is moderated because capabilities are inferred from naming and taxonomy rather than an on-page procedural checklist.1installs36Pendant Querypendant-query appears on Prism as a well-known api/git skill with very little published procedural content in the ingest snapshot—only catalog metadata such as rank and install counters, not a full agent playbook. Solo builders should treat it as a placeholder listing until they open the upstream repository or skills.sh page and confirm what “pendant query” actually executes (likely a narrow Git or API query integration given the source namespace). If it wraps a specific hosted git API, it would fit builders who want agents to run structured repository queries instead of improvising shell git commands. Because documentation is thin here, confidence in journey placement is intentionally moderate: default to Build integrations, re-tag after SKILL.md is available. Check Security Audits on the detail page before granting network or token access.1installs37Prd Review Devprd-review-dev is an agent skill aimed at reviewing Product Requirements Documents through a developer lens before anyone writes production code. Prism lists it from the api/git source with minimal public SKILL body in the ingest snapshot, so placement is inferred from the slug and name: it exists to catch unclear scope, missing edge cases, and untestable acceptance criteria while you are still in the validate phase. Solo builders shipping SaaS or APIs with Claude Code or Cursor invoke it when a PM-style doc lands in the repo and you want structured pushback instead of starting builds on vague specs. Use it after a rough PRD draft and before writing-plans or implementation skills so the agent output becomes a tightened scope narrative developers can estimate. Because public readme detail is thin, treat highlights as category-typical capabilities and read the installed SKILL.md in your environment for exact review checklists.1installs38Prd Summaryprd-summary is cataloged as a productivity-oriented agent skill for shrinking product requirement documents into actionable summaries. The public listing on Prism is thin: it mirrors skills.sh API metadata (slug, rank, install signal) without a full SKILL.md body in the snippet provided, so builders should treat the name and source as the primary signal—it is meant to sit in the Validate phase when you already have a PRD or spec doc and need a tight narrative for scoping, prototype tickets, or agent planning. Ideal use is after discovery notes exist but before you invoke deeper planning skills: the output you want is a concise requirements digest with goals, users, constraints, and non-goals called out. Until richer documentation is ingested, pair it with your own PRD template and review the generated summary manually. Confidence is moderate because procedural steps are not enumerated in the available readme.1installs39Preview Design Docpreview-design-doc is a lightly documented agent skill from the api/git catalog entry whose name and slug indicate a pre-build pass over design documentation. Solo builders install it when they want an agent-assisted preview step that catches gaps, inconsistencies, or missing acceptance criteria before they lock scope and open implementation tasks. Prism lists it with minimal readme text, so treat the skill as a design-doc preview helper you wire into Validate and early Build doc workflows rather than a full template generator. It suits indie SaaS and API projects where a short RFC or design markdown file is the contract between you and your coding agent. After preview, you typically move to prototyping, task breakdown, or implementation plans once the doc reads coherently end to end.1installs40Publish Monitor Scheduledpublish-monitor-scheduled is a DevOps-oriented agent skill from the api/git source that names a scheduled monitoring pattern after publish events. Solo and indie builders who automate releases from git can use it when they want recurring checks instead of ad-hoc log dives after each push. Catalog metadata is thin compared to full procedural SKILL.md repos, so treat it as a specialized hook in the publish monitor chain rather than a general monitoring framework. Pair it with your existing CI or git publish flow and confirm what endpoint or job the skill actually schedules before relying on it in production. Prism tags it under Operate → monitoring so journey browse surfaces it next to other run-the-product tooling.1installs41Requirement Shift Comparerequirement-shift-compare is a slim agent skill from the api/git lineage aimed at solo builders who need to see how requirements moved over time in version control. When a stakeholder says "that was never in scope" or your own notes disagree with the main branch, the skill is meant to structure a compare pass: what requirement text or acceptance criteria existed at one point versus another, expressed as a git-backed diff mindset rather than a full PM suite. Prism lists minimal SKILL body today, so treat it as a focused helper for validation and scoping conversations before you expand build work. It does not replace formal spec documents or automated test suites; it helps you anchor scope discussions in repository history. Confidence is moderate until richer SKILL.md lands in the repo.1installs42Rtk Token Saverrtk-token-saver is listed on Prism via the skills.sh api/git feed as a well-known agent skill aimed at solo builders who ship React apps with Redux Toolkit and want leaner coding-agent sessions. The public ingest payload only confirms the slug, single recorded install, and rank metadata—not a full procedural SKILL.md in this snapshot—so treat the name as the primary signal: compress or avoid redundant context when editing RTK slices, RTK Query API definitions, and generated types. Use it during Build on frontend work when token burn from re-explaining store shape dominates your agent loop. After installation, open the package SKILL.md in your environment for authoritative invoke rules and any RTK-specific guardrails. Prism stores installs and trending separately; do not infer popularity or audit outcomes from this tagging pass.1installs43Skynet Quality ReportSkynet-quality-report is a lightly documented skills.sh entry sourced from api/git, aimed at solo builders who want an agent-invokable quality report pattern associated with the Skynet naming. Public catalog metadata shows a single install and a stable skills.sh URL, which suggests early-stage or niche adoption rather than a full methodology write-up in the ingested readme. Practically, treat it as a pointer skill: your agent loads it when you need a structured quality report step in the Ship phase—paired with your own linters, tests, and review checklists. Because source prose is thin, pair invocation with explicit repo context and output schema you define. It fits indie workflows that want a named, repeatable “quality report” command in Claude Code, Cursor, or Codex without building a custom skill from scratch.1installs44Spec To Xmind Testcasespec-to-xmind-testcase is a compact agent skill aimed at solo builders who already have a spec—feature brief, API contract, or acceptance doc—and need a visual test plan in XMind rather than a loose bullet list. It fits the handoff from scoped requirements to shippable quality: scenarios, preconditions, and expected results organized as mind-map nodes testers can walk through before you invest in Playwright or CI suites. Because catalog metadata is minimal, treat it as a generator-style helper invoked when you are hardening scope from Validate into Ship-ready verification. Pair it with your spec source of truth in git and export XMind files your team or future-you can execute manually or later convert to automated cases.1installs45Sprint Issue ValidatorSprint Issue Validator is a narrowly scoped agent skill meant to check sprint issues before execution, inferred from its slug and api/git packaging on skills.sh. Prism lists it for solo builders who run tight sprints with AI agents and need a consistent gate on issue titles, scope, or sprint membership rather than ad-hoc manual scanning. Public readme on the catalog is sparse, so treat capabilities as checklist-style validation over your issue tracker or git-linked sprint board. Use during Build PM rituals when you are about to pull issues into a sprint or hand them to coding agents. Pair with human review for prioritization and estimates because the skill does not replace product judgment.1installs46Stability Issue TrackerStability Issue Tracker is a catalog entry sourced from api/git on skills.sh, positioned for solo builders who want Git-adjacent tooling to log and follow stability problems rather than scattering incidents across chat. Prism lists it for discoverability when you are hardening production workflows and already organize work around repositories and API/git integrations. Public metadata on the skill is thin—install counts and rank without an embedded SKILL.md body in this ingest—so treat the name as the primary signal: tracking stability issues as first-class work items. Install only after you read the upstream repository instructions, wire any required credentials locally, and confirm what artifacts it creates (issues, labels, dashboards, or hooks). It is not a full observability platform; it complements monitoring and error skills once you know what you need to record when builds, deploys, or runtime checks fail.1installs47Standup List ConfigsStandup List Configs is a thin skills.sh catalog skill from the api/git source, aimed at builders who automate daily standups or async status rituals and need to enumerate configuration presets or entries rather than hard-coding them. Public metadata shows a single install and minimal inline documentation, so treat it as an API-adjacent helper: invoke when you are integrating standup listing into a Claude Code or Cursor workflow and want the agent to fetch or reference the standup-list-configs contract from the well-known skills API. Pair with your own repo docs for auth, payloads, and scheduling. Skip if you already maintain standup YAML locally and do not call external skill APIs.1installs48Standup Remind Releasestandup-remind-release is a git-API catalog skill aimed at solo and indie builders who ship from repos and need lightweight reminders around standups and releases. Public listing metadata is thin, but the name and api/git source signal workflow glue: prompting you before recurring standup updates and release checkpoints so shipping does not depend on memory alone. It is not a full CI/CD system or changelog generator; it is a procedural nudge layer your agent can invoke when you want git-aligned release discipline without standing up another SaaS tool. Use it when you already work in git and want the agent to reinforce human rituals at launch time. Pair it with your existing branch, tag, and deploy checklist rather than treating it as a substitute for automated pipelines or security review.1installs49Standup Remind Unfilledstandup-remind-unfilled is a narrow agent skill meant to catch daily standups that were never filled in before the team meets or posts async updates. Solo builders and tiny teams often skip standup writes when they are heads-down shipping; this skill automates a polite reminder so blockers and progress stay visible without someone playing nag. It is best treated as a glue skill on top of whatever standup or check-in surface your repo or API integration already uses—install when you want consistency, not when you need a full retrospective or planning framework. Prism lists it for builders who already run lightweight rituals and want agent-assisted follow-through instead of manual Slack pings.1installs50Standup Reportstandup-report is an agent skill from the api/git line aimed at solo and indie builders who want standup narratives grounded in real commits instead of memory. When you ship in small bursts, it is easy to under-report what you finished or forget blockers; this skill is meant to compile a concise report from git activity so you can paste into Slack, Discord, or a weekly note. It fits the build phase when you are actively coding and need a repeatable PM ritual without a separate standup bot. Catalog metadata is thin compared to full SKILL.md drops on skills.sh, so treat highlights as intent from the skill name and source repo—verify behavior in your agent after install. Use it alongside your normal git workflow rather than as a replacement for issue trackers.1installs51Standup TriggerStandup-trigger automates the triggering of daily standup meetings or status updates for teams. A solo builder uses it to ensure consistent team communication without manual scheduling overhead. This matters because regular standups keep everyone aligned on progress and blockers, especially critical when operating distributed teams or managing multiple projects simultaneously.1installs52Standup UpcomingStandup Upcoming is a minimal skills.sh git API skill aimed at surfacing what is coming up for standup-style check-ins. Prism lists it with a single install and sparse in-repo documentation, so treat it as a thin integration hook: your agent uses the published api/git endpoint pattern to fetch upcoming items rather than a long on-disk procedural playbook. Solo and indie builders still benefit when they run daily async standups over Slack or Linear and want the agent to summarize imminent commits, branches, or queued tasks from git-adjacent services without writing custom scripts each morning. Confidence is moderate because the local readme is mostly catalog metadata; verify behavior against the live skills.sh API page after install. Use when you already rely on git-centric PM habits during Build and want a repeatable pre-standup pull, not when you need deep sprint retrospective analytics.1installs53Team InfoTeam-info is a skill for accessing and querying team member information, roles, and composition through an API or command interface. Solo builders use it to understand who's on their team, what roles they have, and how the team is structured. This matters for project planning, resource allocation, and coordination as projects scale from solo work to small teams.1installs54View Team Sessionview-team-session is a minimally documented api/git catalog entry whose title points at viewing a team Git session from an AI coding agent. Prism lists it for solo and indie builders who want Git collaboration hooks alongside Claude Code, Cursor, or Codex, but the ingested readme is API metadata only—install count, rank, and source URL—without steps, triggers, or tool permissions. Treat it as a placeholder integration skill: confirm the live skill body on skills.sh before relying on it in production workflows. Once fully documented, it would likely help during build-phase Git integrations when you need session context without leaving the agent. Until then, browse journey hubs under Git & Pull Requests and validate the remote definition matches your host (GitHub, GitLab, or similar).1installs55Vip Alarm Daily Reportvip-alarm-daily-report is a narrowly scoped agent skill from the api/git skills.sh feed intended to help solo builders and tiny teams produce a daily summary of VIP-related alarms. The public listing carries minimal procedural detail, so treat it as a hook to wire your own reporting job—queries, thresholds, and notification sinks you already use—into a repeatable agent workflow. It fits operators who run a SaaS or API product with tiered customers and need a consistent morning readout instead of ad-hoc dashboard clicks. Install when you want your coding agent to draft or trigger a daily VIP alarm report as part of production hygiene, then layer your real data sources and formats in the repo or companion docs. Prism surfaces it for discoverability alongside other automation skills; validate behavior and permissions in your environment before relying on it in production.1installs56Vip Alarm Toolvip-alarm-tool enables builders to configure intelligent, priority-weighted alerting systems for their applications and infrastructure. Solo builders use it to establish monitoring rules that catch critical issues before they impact users. This matters because timely alerts on VIP-level events directly reduce downtime and improve system reliability in production environments.1installs57Vip Code Reviewvip-code-review is an agent skill published from the api/git source on skills.sh, positioned for builders who want a dedicated code-review capability in the agent loop rather than one-off prompts. The public ingest record does not include a full SKILL.md body, so treat the slug and catalog placement as the primary signal: it belongs on the Ship phase review shelf alongside testing and security checks. Solo and indie builders shipping SaaS, APIs, or CLIs can install it when they want repeatable review rituals before merge or deploy. Because procedural detail is not present in the snippet you are tagging from, verify triggers, outputs, and severity buckets in the upstream repository before wiring it into a hard gate. Prism surfaces it as a Code Review & Quality skill compatible with Claude Code, Cursor, Codex, and other agents that load skills.sh packages.1installs58Vip Code Review Add Rulevip-code-review-add-rule is a narrow agent skill from the api/git catalog for solo and indie builders who already run structured code review with agents and need to append or refine a single review rule. Public listing metadata is sparse, but the slug and packaging imply a focused installer: describe the rule you want enforced (style, security, architecture, or team convention) and wire it into your existing VIP code-review stack instead of re-authoring an entire review skill. It fits indie teams shipping SaaS, APIs, or CLIs who treat review as a repeatable gate before launch. Use it after you have a repo and a baseline review process; expect a rule definition or config fragment rather than a full audit runner. Because installs are minimal, treat outcomes as policy documentation the agent honors alongside your primary review skill, and verify behavior in a dry-run PR before relying on it in CI.1installs59Vip Code Review Submit IssueThis tool facilitates the submission and management of code reviews and issues within development workflows. Solo builders use it during the code review phase to ensure quality standards and track feedback. It matters because efficient code review processes reduce bugs, improve code quality, and accelerate the path to production.1installs60Vip Release Conflictvip-release-conflict is a git- and release-oriented agent skill from the api/git source on skills.sh. It is meant for solo and indie builders who own their own deploy pipeline and hit merge or release-line conflicts when a high-priority fix must go out on a named release branch. The catalog entry is thin on procedural detail, but the name and source clearly anchor it in release management rather than generic coding assistance. Use it when a VIP or scheduled release is blocked by conflicts between main, release, or hotfix branches. Pair it with your existing review and CI checks so conflict resolution stays auditable. Treat outputs as operational guidance you still verify with git status, tests, and your hosting provider’s release rules.1installs61Vip Skills Updatervip-skills-updater is a lightly documented skills.sh catalog entry sourced from api/git, aimed at solo builders who treat agent skills like dependencies to refresh over time. Public metadata positions it as an updater for VIP or curated skill sets rather than a workflow that transforms application code. In practice you would reach for it when your Claude Code or Cursor environment pins skills from the skills.sh API and you need a repeatable way to pull newer revisions without hand-copying SKILL.md folders. Because the ingested readme is almost entirely registry JSON, treat capabilities as meta maintenance until you inspect the full package in your install path. It sits alongside other Skill Development utilities for builders running multiple skills from git-backed sources. Confidence is moderated by sparse SKILL.md detail; verify behavior after install.1installs62Vip Testvip-test is a minimal Prism/skills.sh listing tied to the api/git source with a single recorded install and no usable SKILL.md body in the catalog excerpt. Solo builders should not rely on it for automation, testing, or deployment until the upstream repository documents triggers, permissions, and outputs. Prism tags it conservatively under build integrations so faceted browse does not imply journey coverage the package cannot support. After the maintainer adds real instructions, re-tag with invokeWhen, deliverables, and workflow chains from that document.1installs63Vip Test Analyzevip-test-analyze is an agent skill aimed at solo and indie builders who maintain PHP applications—especially WordPress VIP or similarly gated hosting—where merges depend on green CI and meaningful PHPUnit coverage. When logs are noisy or you are unsure which failures block release, the skill guides structured interpretation of test artifacts: which suites failed, whether failures cluster around integrations or regressions, and where coverage is thin relative to critical paths. It is meant for the Ship phase after you have tests running locally or in pipeline, not for greenfield test design from scratch. Use it when you need a second pass that turns raw test output into a prioritized fix list your coding agent can execute. Pair it with your existing test runner and review workflow; it does not replace writing tests or choosing a framework. Confidence in journey placement is moderate because public SKILL.md detail is sparse; treat the name and api/git source as signals toward VIP-oriented test analysis.1installs64Vip Test Casevip-test-case appears on Prism as a skills.sh api/git catalog skill with almost no inlined SKILL.md body in the ingest payload—only ranking and install metadata. Solo builders should install the actual repository skill and read its instructions before relying on tags here. The slug strongly suggests automated or documented test cases aligned with WordPress VIP or enterprise WordPress hosting constraints, which typically matter during Ship when you prove releases against platform rules. Until full prose is available, use this listing to discover the skill, then validate scenarios, PHPUnit or integration expectations, and CI hooks in the source repo. Confidence stays moderate because Prism cannot infer detailed capabilities from the API stub alone.1installs65Vip Test Impactvip-test-impact is a lightly documented agent skill from the api/git source on skills.sh, aimed at builders who want test effort aligned with what actually changes in the repo. Solo and indie teams shipping APIs or CLIs often run oversized test matrices; a VIP or impact-oriented skill is meant to narrow focus to tests that guard revenue paths, auth, billing, or other labeled critical areas. Because the published readme is mostly catalog metadata rather than a full procedural SKILL.md, you should clone or install the package and read the skill body before relying on it in CI. Use it in the Ship phase when you are deciding what must run before merge, especially alongside git-based change detection. It is not a replacement for coverage tools, security scanners, or full regression suites—it is a planning aid for test scope. Confidence is moderate only after you confirm invoke steps and outputs in your environment.1installs66Vip Test Initvip-test-init is a lightly documented skills.sh entry sourced from api/git with almost no procedural SKILL.md in the catalog ingest. Prism tags it conservatively for solo builders who search by name for WordPress VIP or enterprise PHP test bootstrapping. Without README steps, treat installation as fetching the upstream skill package and reading whatever vip-test-init ships in-repo. Use it when you already target VIP-aligned hosting and need an agent-guided first pass at test layout—not when you want a general Jest or Playwright tutorial. Confidence stays moderate because triggers, permissions, and deliverables are not spelled out in the indexed text; confirm behavior locally before relying on it in CI.1installs67Vip Test Reportvip-test-report is a lightly documented catalog entry from the api/git source that signals an agent skill oriented around VIP test reporting—typically the kind of structured test output enterprise WordPress VIP pipelines expect before code reaches restricted environments. Prism lists it for solo and indie builders who occasionally contract on VIP-grade sites or mirror similar gating locally, even when the full procedural SKILL.md is not inlined in the directory ingest. Practically, you install it when you want your coding agent to know a vip-test-report capability exists in the api/git skill pack and to align conversations with test artifacts, CI summaries, and release checklists rather than ad-hoc paste of junit logs. Because the public stub mainly carries registry metadata, you should open the source URL and repository instructions after install to learn exact commands, report formats, and required environment variables. Confidence is moderate until richer SKILL.md is available in catalog mirrors.1installs