Discover
Discover and install skills, docs, and rules to enhance your AI agent's capabilities.
| Name | Contains | Score |
|---|---|---|
Skills that Learn from past work loops run: review pull request history for agent context and Tessl verifier improvements, read recent agent runs to record recurring problems as project findings, propose Code Review lens changes from how the lenses did on recent pull requests, and turn open findings into tickets the factory builds. Contains: findings-triage Triage a project's open Tessl findings in a Tessl factory. Check each against the current code, then resolve it, ignore it with a reason, hand it to a person, or file a ticket that the project's own Implement Loop will build. Works out from the factory's triggers where tickets come from (Linear or GitHub issues) and what a ticket must satisfy to start work. Writes tickets and finding updates only; changes no code and opens no pull request. Use when a Learn from past work loop runs Turn findings into tickets, or when asked to triage, act on or clear a project's findings. learn-from-agent-runs Read the transcripts of recent agent runs that opened pull requests, together with those pull requests' review feedback, find problems that recur across runs (dead ends, repeated failed commands, missing tools or access, slow or flaky checks, misread instructions, review feedback the agents keep earning) and record each as a project finding with the cheapest lasting fix. Use when a Learn from past work loop runs an agent retrospective, or when asked to review recent agent runs, launch transcripts or PR review feedback for recurring workflow problems. learn-from-review-feedback Investigate a repository's pull request history, tracing review corrections through commit history, current code, agent guidance and Tessl verifier configuration, and record up to three evidence-backed recommendations (an agent context update, a Tessl verifier, or both for the same failure) as Findings V2 project findings. Use when a Learn from past work loop run reviews development patterns, or when asked to mine PR review feedback for mistakes agents repeat and propose AGENTS.md, rule, skill or Tessl verifier changes from that evidence. tune-review-lenses Read how this repository's Tessl Code Review lenses have done on recent pull requests (the findings authors addressed, declined or refuted, and the bugs that got past review) and record Tessl findings that propose specific changes to the lenses. When the repository still reviews with the default lenses from the registry, the first finding proposes copying them into the repository so they can be tuned. Records findings only; changes no file and opens no pull request. Use when a Learn from past work loop runs lens tuning, or when asked why Code Review keeps raising findings people decline, or how to tune a repository's review lenses. | Skills | |
ParthJadhav/app-store-screenshots Use when building App Store or Google Play screenshot pages, generating exportable marketing screenshots for iOS, macOS, and/or Android apps, or scaffolding a screenshot editor with Next.js. Triggers on app store, mac app store, play store, screenshots, marketing assets, html-to-image, phone mockup, mac mockup, android screenshots, feature graphic. | Skills | |
davepoon/buildwithclaude Automate OneDrive file management, search, uploads, downloads, sharing, permissions, and folder operations via Rube MCP (Composio). Always search tools first for current schemas. | Skills | |
davepoon/buildwithclaude Automate Box cloud storage operations including file upload/download, search, folder management, sharing, collaborations, and metadata queries via Rube MCP (Composio). Always search tools first for current schemas. | Skills | |
ivan-magda/claude-superpowers Use when encountering Swift 6 concurrency errors, Sendable conformance warnings, actor isolation issues, "global variable is not concurrency-safe" errors, or migrating codebases to Swift 6 language mode | Skills | |
usedetail/cli Interact with Detail bugs for a repository via the CLI — list and filter bugs, inspect reports, close as resolved or dismissed, reopen previously closed bugs, and override a bug's priority. | Skills | |
AI Unified Process Spring Boot layers - service, REST API, and external system client implementation and tests Contains: spring-client Builds the client layer of a use case (UC-XXX) in a Spring Boot application: for every external system its Secondary Actors line names and docs/architecture/stack.md maps under External systems, an outbound port in the business module and an adapter that calls the system as its contract says — an OpenAPI operation through RestClient or an @HttpExchange interface, an AsyncAPI channel through a Kafka or AMQP producer. The adapter maps the provider's DTOs to domain records, so no provider type crosses the port, and turns the alternative flows the system causes (rejection, timeout, unavailable) into domain exceptions; it decides no retry policy alone. Use when the user asks to "call the payment provider", "integrate an external API", "write a REST client", "build the outbound adapter", or mentions RestClient, @HttpExchange, an external system as secondary actor, or a provider's OpenAPI or AsyncAPI file in a project that combines layer plugins. Normally run by /use-case-implement before the service layer. spring-client-test Writes the client layer tests of a use case (UC-XXX) in a Spring Boot application: for each external system the use case calls, adapter tests against a stub of the provider's contract — MockRestServiceServer or WireMock for an OpenAPI operation, the broker's test setup for an AsyncAPI channel — that check the request on the wire, the mapping to domain records, and every alternative flow the system causes (rejection, timeout, unavailable); plus a reusable in-memory fake of the outbound port that the service, API, and UI tests put in place of the real adapter, so no test reaches the real system. Classes are named <System>ClientTest and every method carries @UseCase. Use when the user asks to "test the REST client", "test the payment provider adapter", "stub the external system", "write WireMock tests", or mentions MockRestServiceServer, WireMock, a fake of an outbound port, or contract-based client tests in a project that combines layer plugins. Run by /use-case-test before the integration layer. spring-rest Implements the REST API layer of a use case (UC-XXX) in a Spring Boot application: @RestController endpoints on top of the service layer, request and response DTO records, @Valid input validation, error mapping to RFC 9457 Problem Details with a @RestControllerAdvice, a status code per alternative flow, and paging. Takes the base path and contract style from the API contract section of docs/architecture/stack.md, and builds an operation the use case's **API:** line links in an agreed OpenAPI contract exactly as written; holds no business rule the service does not enforce. Use when the user asks to "build the REST API", "create an endpoint", "expose the use case over HTTP", "add a controller", "map errors to Problem Details", or mentions @RestController, @RequestMapping, DTOs, ProblemDetail, RFC 9457, status codes, or a JSON contract for a separate client such as Angular. Normally run by /use-case-implement after the service layer; it can also be run directly. spring-rest-test Writes the REST API tests of a use case (UC-XXX) in a Spring Boot application: status codes, Location headers, the JSON contract (field names, date formats), RFC 9457 Problem Details bodies, and — as the integration layer of a REST service or behind an Angular client — every business rule's allowed and rejected request at the boundary, through the real service and database. Uses MockMvcTester against the full stack or live HTTP with RestTestClient and Testcontainers, detecting and keeping a project's existing convention (including MockMvc or RestAssured) and asking before the first API test. Classes are named UC001<Name>ApiTest and every method carries @UseCase. Use when the user asks to "test the REST API", "test the controller", "test the endpoints", "write API tests", "check the status codes", or mentions MockMvc, MockMvcTester, RestTestClient, RestAssured, ProblemDetail tests, or Spring Boot web tests. Normally run by /use-case-test as the integration layer; it can also be run directly. spring-service Implements the service layer of a use case (UC-XXX) in a Spring Boot application: @Service classes with constructor injection, @Transactional boundaries, the business rules with UC-XXX BR-YYY markers, domain exceptions for every rejection the API or UI turns into a message, and Bean Validation on the inputs. Calls the persistence layer only through the repository or port its Handover names, and supports both a flat single module and a hexagonal multi-module layout (domain record, business service, outbound port). Use when the user asks to "implement the service layer", "write the business logic", "enforce the business rules", "create a Spring service", "add transactions", or mentions @Service, @Transactional, domain exceptions, or the business module of a hexagonal Spring Boot project. Normally run by /use-case-implement after the persistence layer; it can also be run directly. spring-service-test Writes the service layer tests of a use case (UC-XXX) in a Spring Boot application: every business rule with its allowed and its rejected case, every alternative flow the service decides, and the main success scenario, called on the @Service directly. Uses @SpringBootTest with the real persistence layer and a Testcontainers database, or plain unit tests with an in-memory fake of the outbound port in the business module of a hexagonal project. Classes are named UC001<Name>ServiceTest and every method carries @UseCase. Use when the user asks to "test the service layer", "test the business rules", "write service tests", "unit test the business logic", or mentions @SpringBootTest service tests, Testcontainers, domain exceptions, or business rule tests for a Spring Boot use case. Run by /use-case-test as the integration layer of a Hilla stack or a stack without an entry layer, or when the service layer is named; below a Vaadin Flow UI or a REST entry layer their tests cover the service. Can also be run directly. | SkillsRules | |
astronomer/agents The language-neutral foundation for Airflow language SDKs — implement task logic in a non-Python language while the DAG stays in Python. Use when the user wants to run an Airflow task in another language (Java, Kotlin, Go, or other JVM/native languages), asks how the Python `@task.stub` pairs with native task code, how task/DAG IDs must match across the two sides, how data passes via XCom as JSON, or which language SDKs exist. This skill owns the shared Python-stub pattern and conceptual model; for a specific language's native API, build, and runtime, use that language's skill (e.g. authoring-java-sdk-tasks, authoring-go-sdk-tasks). | Skills | |
adobe/skills Captures the rendered layout of a webpage as a spatial tree of elements, with positions, sizes, grid layouts, backgrounds, and overlay occlusion, via the web CLI. Returns indented text, a JSON tree, and a map from node IDs to CSS selectors. Use before page decomposition, overlay detection, or brand extraction, or when the user asks for a page's visual hierarchy or layout. | Skills | |
adobe/skills Detects the languages on a webpage, both declared in markup (html lang, hreflang links, nested lang attributes, Content-Language meta) and present in the body text (Google CLD3), and reports where the two disagree. Use for i18n audits, hreflang validation, multilingual page checks, or when asked what language a page is in. | Skills | |
adobe/skills Launches a persistent, headless-by-default Chromium (playwright-cli's) with an unpacked extension loaded through `web ext`, opens the extension's side panel, popup, or options page, and interacts with it over `web browser eval/cdp`. Handles the Chrome 137+ restriction on loading unpacked extensions and the side panel user-gesture requirement. Use when testing, automating, or validating a Chrome extension's UI. | Skills | |
adobe/skills Finds, searches, and previews real, licensable Adobe Fonts typefaces: contextual recommendations, direct lookup by name or facets (foundry, designer, style), metadata (language support, weight, foundry), style variants in a family, and a visual specimen. Use for font recommendations, looking up a specific font, "what does [font] look like", a font's language support or designer/foundry, weights/widths in a family, or choosing/pairing fonts for a design (poster, invitation, social post, brand, website, presentation). Discovers and previews fonts only — does not lay out the design. Triggers: "what font for...", "find fonts like [name]", "search Adobe Fonts for...", "does [font] support [language]", "who designed [font]". | Skills | |
adobe/skills Resize, crop, or export any image or video into platform-ready social media assets using Adobe Creative Cloud tools. Use this skill when a user wants to prepare a photo, image, or video for one or more social platforms — Instagram, TikTok, LinkedIn, Facebook, YouTube, Snapchat, Pinterest, Threads, or X/Twitter. Triggers on: "prepare my image for Instagram", "resize for TikTok", "get this ready to post", "make versions for all platforms", "social media sizes", "crop for stories", "export for LinkedIn", "resize my video for social", "make social media assets", or any request to adapt a photo or video for specific platforms. Handles subject-aware cropping, AI canvas expansion, test previews before full runs, and same-ratio video resizing. | Skills | |
adobe/skills Use this skill whenever the user wants browser-based end-to-end tests for an Adobe App Builder application. Covers Playwright E2E testing for ExC Shell SPAs, AEM extension UIs, and full-stack flows. Use when the user mentions: "E2E test", "end-to-end test", "Playwright", "browser test", "test my SPA in the browser", "test my AEM extension", "test the full flow", "integration test with UI", "headless browser test", "E2E in CI". This skill is for BROWSER-based testing only. For Jest unit tests of actions or React components, use appbuilder-testing instead. | Skills | |
adobe/skills Use this when installing, running, or configuring the Adobe AEM CLI (@adobe/aem-cli, formerly the helix-cli npm package; commands `aem up`, `aem import`, `aem content`), when `aem up` fails (port conflicts, cert errors, proxy 404s, pipeline vs. local-file confusion), or when migrating from the old helix-cli package. Covers installation, the local Edge Delivery dev server, .env / AEM_* configuration, HTTPS/TLS, proxy and certificate trust, content sync with da.live, and troubleshooting. For da.live content-format rules or the DA Source API contract use da-content; for writing EDS block code use content-driven-development. | Skills | |
adobe/skills Generate JSON-LD structured data for AEM Edge Delivery Services pages. Analyzes page content and metadata to determine the appropriate schema.org types, extracts relevant properties, and produces validated JSON-LD snippets ready for implementation in head.html or scripts.js. Use when adding rich results support, improving search appearance, or auditing existing structured data. | Skills | |
adobe/skills Optimize AEM Edge Delivery Services commerce product pages for search engine crawling and indexing. Audits client-side rendered product content for crawlability, validates meta tags, Product schema.org structured data, canonical URLs, and image optimization. Addresses the core challenge that EDS product pages render catalog data via JavaScript, which search crawlers may not fully execute. Use when product pages are not appearing in search results or have poor search visibility. | Skills | |
adobe/skills Creates complete AEM components with dialog, HTL template, Sling Model, unit tests, and clientlibs. Supports extending Core Components and project components. When a Figma design URL is provided, fetches the design via Figma MCP (get_design_context) and translates it into pixel-perfect HTL, CSS, and JS. Follows Adobe Experience League best practices for AEM Cloud Service and 6.5. Use this skill whenever the user mentions creating, building, generating, or scaffolding an AEM component, or mentions component types like teaser, card, hero, banner, accordion, tabs, carousel, list, navigation, breadcrumb, or any custom AEM component. Also trigger when the user wants to extend a Core Component, create a component dialog, add a Sling Model, or convert a Figma design into an AEM component. | Skills | |
kopai-app/kopai-mono Build Kopai observability dashboards from OpenTelemetry metrics, logs, and traces by composing tiles — time-series charts, stat/KPI numbers, histograms, log timelines, and trace-detail views — into a dashboard via the Kopai SDK. Use this skill whenever the user wants to visualize, chart, monitor, or 'keep an eye on' telemetry — e.g. 'make a dashboard', 'monitoring view', 'KPI panel', 'chart request latency and throughput', 'an incident board with error logs and a trace viewer' — even if they don't say the word 'dashboard' — and when another workflow needs to present telemetry visually (e.g. after a root-cause analysis). This creates Kopai dashboards specifically. Do NOT use it to investigate or root-cause an issue (use root-cause-analysis), to add instrumentation (use otel-instrumentation), to build Grafana/Prometheus dashboards, or to code React/UI chart components. When the Kopai connector is attached, use create-live-page instead unless the user asks for a Kopai dashboard. | Skills | |
alirezarezvani/claude-skills The meta-framework for how a company runs — the connective tissue between all C-suite roles. Covers operating system selection (EOS, Scaling Up, OKR-native, hybrid), accountability charts, scorecards, meeting pulse, issue resolution, and 90-day rocks. Use when setting up company operations, selecting a management framework, designing meeting rhythms, building accountability systems, implementing OKRs, or when user mentions EOS, Scaling Up, operating system, L10 meetings, rocks, scorecard, accountability chart, or quarterly planning. | Skills |
Can't find what you're looking for? Evaluate a missing skill.