Copy this prompt into the AI assistant you're using.
Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/Agenta-AI/agenta.Loading the repository README…
Showing 40 of 45 collected skills.
Run the agent release gate — a portable, wire-level QA harness for the agent runtime. Drives the same product endpoint the playground drives and asserts on the SSE frame stream and real side effects, never on model prose, so it works against any deployment…
Pick and record the names of a new concept in every layer (database table and column, ORM model, DTO, route, JSON field, UI label), and give every stored item kind the same resource shape and the same actions. Holds the glossary format with an Avoid list, the…
Makes prose plain and easy to read, with common words, whole sentences, no dashes, no made-up terms and no comparisons. Use it when you write or revise a document, report, summary, README, email, slide, Notion page, commit message or PR description, or when…
Prepare a plain-language PR review briefing from a GitHub pull request URL or number. Use when the user says "help me review this PR", "summarize this PR for review", "what does this PR do", or wants the reason, systems involved, changes, risks, CI state, and…
Review one code change, or one design (an OpenSpec change, a spec draft or an architecture doc), for naming, consistency and layering, and rate it Low, Medium, or High. Looks for one concept with several names across layers (table, column, DTO, route, JSON…
Drive a researched and planned feature to a landed, tested change. Use after plan-feature has produced a docs/design/<project>/ workspace and the user says "implement it", "build the plan", "run the plan", or "let's ship this". Orchestrates refresh-plan,…
Keep documentation in sync with a code or contract change in the SAME PR. Use whenever you change an interface, wire field, endpoint, config field, default, harness/backend value, or runtime behavior, and after any implement-feature slice that lands such a…
Design and review interface parameters by semantic role: classify each field by what it IS (data, config, policy, credentials, routing, metadata, protocol context), who owns it, when it changes, and whether a standard name exists, not by the feature it…
Review one code change for correctness and rate it Low, Medium, or High. Looks for bugs, regressions in existing behavior, broken flows, concurrency and retry problems, and migrations that can fail or lose data. Use when asked to "review this PR for bugs",…
Review one code change, or one design (an OpenSpec change or an architecture doc), for needless complexity and rate it Low, Medium, or High. Looks for scope that could be narrower, edge cases that do not deserve machinery, state kept in several places,…
Review one code change for agent slop and rate it Low, Medium, or High. Slop is avoidable, low-trust work that comes from not understanding the repo, such as wrong assumptions, broken flows, duplicate systems, weak tests, comment noise, and leftover dead…
Use this skill to create and publish changelog announcements for new features, improvements, or bug fixes. This skill handles the complete workflow - creating detailed changelog documentation pages, regenerating the in-app What's New data, and ensuring…
Create or revise an evidence-backed SEO brief for owner approval before scaffolding or drafting.
Prioritize content opportunities or a small cluster and decide create versus update from business fit, demand evidence, existing coverage and proof.
Scaffold, draft, revise and prepare assets from an approved brief using existing owner playbooks. Preserve approved text and designer assets.
Diagnose outdated or declining content and prepare or execute a scoped refresh through briefing, production and review, without implicit republishing permission.
Check facts, editorial quality, positioning, SEO, links, attribution, visuals and conversion before the owner's publish-readiness decision.
Learn the purpose, audience and context of a business or website through public research, useful private materials and conversation with its owner. Use for onboarding or updating that understanding.
Research competitors' SEO and content strategies: blog topics, intent, ranking keywords and top pages where data is available. Identify search competitors and opportunities for useful content.
Inspect crawlability, indexability, rendering, canonicals, redirects, links, schema and mobile/performance problems. Report evidence, not automatic production changes.
How to give the person a small interactive page in the drive: a board, checklist, queue, form, table or dashboard. Read it when the ask is for something to look at and touch rather than a reply. Covers picking a starter with create_app, the app folder layout,…
Refresh Agenta's harness catalogs, provider model lists, recommended defaults, and provider-supplied display names. Use for new OpenAI, Anthropic, Codex, Pi, or OpenRouter models and before releases that need current model choices.
Use when searching the web for job openings, comparing job-board search strategies, validating listings, and extracting job details with Tavily.
Where to put frontend code (package vs the web/mobile app layer) and how to use the @agenta/* packages. Use when authoring or moving code in web/packages, choosing which @agenta/* package owns something (ui, entities, entity-ui, shared, chat, sessions,…
Feature-folder layout, states/ convention, and data-flow rules for the Agenta mobile app (web/mobile). Use when creating or moving files under web/mobile, deciding where a component lives, adding a new feature or screen, or wiring data into mobile components.
Motion design rules for the Agenta mobile app (web/mobile) — the shared presets in src/lib/motion, when to animate, and reduced-motion requirements. Use when adding any animation or transition under web/mobile, animating navigation, sheets, skeletons, or…
How the Agenta mobile app (web/mobile) installs and extends shadcn/ui registry components, themes them via the palette token bridge, and builds chat UI on @agenta/chat. Use when adding UI components under web/mobile, changing theme colors, editing…
Audit and update the supported LLM model list in assets.py against litellm's registry (models.litellm.ai). Use when adding new models, pruning outdated ones, or verifying the list is correct.
Research a prospective company and prepare a short, source-backed fit assessment.
Write a template playbook for the build-an-agent skill: a 1-2 KB per-use-case file that teaches the builder agent to configure one kind of Agenta agent (changelog writer, issue triager, support router, and so on). Use when the ask is "write a template…
Hard-won GitButler mechanics for multi-lane work in this repo — committing to a specific lane in a stack, spreading a pile of edits back across an existing stack, ordering a stack and setting PR bases, and recovering from a scrambled workspace. Use when…
Write PR titles and descriptions the way a staff engineer would. Use when drafting or editing a pull request title and body, before running `gh pr create`, or any time the user asks for a PR description, summary, or release-notes-style writeup of a change.…
Resolve findings by implementing the chosen fix path in code, tests, or docs. Accept optional `path` and a `priority` selector; by default resolve only the next highest remaining priority bucket, in order `P0`, `P1`, `P2`, `P3`. Also accept explicit levels or…
Perform a fresh-context scan of code and docs that turns verification observations and missing-test gaps into findings. Accept optional `path` and `depth` parameters and default to `path=infer`, `depth=deep`. Confirm effective variables before starting.
Sync the findings record against local review artifacts and optionally a GitHub PR. Accept optional `path` and GitHub PR `url`; when `url` is provided, sync against both remote PR state and local state, otherwise default to local-only sync. Default to…
Run or inspect the relevant validation paths and turn failures, regressions, or missing coverage into findings. Accept optional `path` and `depth` parameters and default to `path=infer`, `depth=deep`. Confirm effective variables before starting.
Coordinate findings work with the user, decide whether scan, test, or sync should run, and turn the current findings set into a ready plan. Accept optional `path` and GitHub PR `url`; default to `path=infer`. Confirm effective variables before starting.
Helps add announcement cards to the sidebar banner system. Use when adding changelog entries, feature announcements, updates, or promotional banners to the Agenta sidebar. Handles both simple changelog entries and complex custom banners.
Create a plan for a feature, and the files required to continue working on it. Use when the user asks for research for a feature or a plan to run it.
Apply Joseph Williams' clarity principles when writing or editing prose. Use when drafting technical or business writing, diagnosing unclear sentences, rewriting passive or abstract prose, or any time the user references Williams, "Style: Lessons in Clarity…
The repository README could not be loaded. You can still explore its Skills below.