Ship agent workflows in 30 seconds. Browse 2,000+ expert-built and security scanned skills. Browse skills
THE AGENSI STORE
95 skills found
by Shandra
Protects API endpoints from accidental breaking changes by generating contract maps, validation rules, integration tests, documentation, and safe AI coding prompts.
by Indy Agent
From feature idea to 10-section engineering-ready PRD — with anti-goals, success metrics, and open questions.
Audit any AI-generated output for unsupported claims, then verify every factual and technical assertion against its real source before it ships.
Generate a complete pull request description from your staged changes, commits, and branch diff: summary, changes, test plan, and checklist, ready for GitHub, GitLab, or Bitbucket. Cross-checks the file list against what git actually reports, so reviewers get the why and what without hallucinated filenames.
Generate beautiful release notes and changelogs automatically from commits, pull requests, and deployments.
Find and remove commented-out dead code across 8 languages (JS, TS, Python, Java, Go, Rust, HTML, CSS) while preserving TODOs, FIXMEs, license headers, disabled tests, and real documentation. Previews every change first and writes .bak backups before it touches a file.
by LocoLoboZ
Draft, update, and convert professional Functional Requirements Specifications (FRS) for procurement and GRC.
Turn git history into clean release notes: parses Conventional Commits across a tag range or commit window, groups them into Features, Fixes, and Breaking Changes, translates the jargon into plain English, and suggests the next SemVer bump. Markdown ready for GitHub, GitLab, or your CHANGELOG.md.
by LB Creations
Turn Apple endpoint work into clean change tickets.
by LocoLoboZ
Convert SOPs and checklists into configuration-ready BMC Remedy Service Request and Work Order design documents.
by Shandra
Creates structured troubleshooting runbooks for legacy banking systems with incident classification, dependency mapping, log review checklists, escalation paths, rollback guidance, and post-incident summaries.
Repo gets views but no stars? Get the one ready-to-paste README fix for the biggest blocker killing your conversion.
by Timoranjes
Automatically validate OpenAPI specs, detect breaking changes, and sync API implementation with documentation.
by Shogun Labs
Automate secret scanning with gitleaks — detect API keys, passwords, tokens before incidents.
by Shogun Labs
Merge files, URLs, and research into a single coherent document with deduplication and source attribution.
Catch documentation that drifted from your code. Flags functions and methods named in your docs that are gone from the source, CLI flags documented but missing from the arg parser, env vars the docs mention but the code never reads, example imports of modules that no longer exist, and npm scripts or Make targets your docs reference but the project does not define. Cross-references your README and docs against Python and JS/TS source.
Audit your dbt project for the test and documentation gaps that let bad data ship. Flags models with no unique or not_null tests, sources missing freshness config or tests, likely keys without a not_null test, models missing descriptions, SELECT * in models, and raw table references that should use ref() or source(). Each finding comes with a suggested tests: YAML snippet to drop into schema.yml.
Generate an llms.txt for your site and validate an existing one against the spec. The generator turns your sitemap.xml or docs folder into a clean, sectioned llms.txt with one-line descriptions. The validator flags a missing H1 title, a missing summary blockquote, malformed link entries, links with no description, relative URLs that should be absolute, and a referenced llms-full.txt that is not present.
A repo visitor decides in about ten seconds whether your project solves their problem — and most READMEs spend those ten seconds on installation instructions instead of answering 'what does this actually do'
Developers don't read documentation — they arrive with a task, scan for the answer, and leave. Docs that aren't structured for that pattern don't get read, they get abandoned
Generate a shareable stat card for any repo, with an honest health grade. It reads the file tree and renders a card showing the language mix, file count and size, whether tests, docs, and a license are present, and an A-to-F health grade from a documented rubric. Markdown by default, SVG with a flag. The kind of card people actually post.
Point it at an unfamiliar or inherited repo and quickly understand it. Maps the architecture, identifies the key modules and entry points, traces the core end-to-end flows, surfaces the conventions and gotchas, and assembles a clean ONBOARDING.md — turning a strange codebase into a clear mental model fast. Built for the moment you join a project, take one over, or have to explain a repo before changing it.
Capture "tacit knowledge" and load-bearing hacks into high-impact onboarding and handoff documentation.
by Nex AI
Automate EU AI Act transparency audits, Article 50 disclosures, and AI literacy documentation for your apps.