Discover and install skills, docs, and rules to enhance your AI agent's capabilities.
| Name | Contains | Score |
|---|---|---|
0gsd/enough Offline translation across ~419 languages via MADLAD-400-3B-MT (CTranslate2 + SentencePiece). No cloud. No account. The model downloads once (~3 GB) and runs locally on CPU or Apple Silicon thereafter. Use whenever the user wants to translate text TO or FROM a non-English language — short phrases, paragraphs, whole documents, idioms, low-resource languages, indigenous languages, dead languages MADLAD has seen, polite forms, casual registers. Also trigger on "translate", "say this in <lang>", "what does <foreign text> mean", "render this in <language>", "<lang> for <phrase>", "how do you say X in Y", "localize", or any request that involves moving text between human languages. DO NOT use for code translation between programming languages. DO NOT use for transliteration (script conversion) without a target meaning — MADLAD translates meaning, not glyphs. | Skills | |
jabrena/plinth Use when reviewing, designing, or modifying Java enterprise systems that expose, exchange, store, process, export, or port data across users, businesses, connected products, cloud providers, APIs, event streams, AI data pipelines, data spaces, or SaaS platforms and need EU Data Act engineering controls. This should trigger for requests such as Review a Java platform for EU Data Act controls; Design data access and portability evidence; Add data-sharing request workflows, export formats, interoperability, metadata, audit logs, cloud-switching support, non-personal data safeguards, or trade-secret handoffs; Assess Data Act engineering readiness before production release. Part of Plinth Toolkit | Skills | |
jabrena/plinth Use when reviewing, designing, or modifying Java enterprise systems that may support financial entities, critical ICT services, third-party ICT provider integrations, or operational resilience obligations under DORA. This should trigger for requests such as Review a Java platform for DORA ICT risk controls; Design operational resilience evidence for a financial service; Add incident, continuity, backup, recovery, or third-party ICT controls; Assess resilience testing and monitoring before production release. Part of Plinth Toolkit | Skills | |
jabrena/plinth Use when a problem under exploration needs its surrounding system context identified before design begins — Existing systems, Integrations, Ownership, and External dependencies. This should trigger when an issue's Context Mapping point of view needs evaluation, or when a maintainer directly asks to map the systems, integrations, owners, and external dependencies relevant to a problem. Part of Plinth Toolkit | Skills | |
jabrena/plinth Use when Java design, refactoring, or implementation tradeoffs should be evaluated with Kent Beck's simple design rules, including passes the tests, reveals intention, has no duplication, and has the fewest elements. This should trigger for requests such as Apply simple design rules; Review this design with Beck's rules; Choose between these refactoring options; Keep this Java design simple. Part of Plinth Toolkit | Skills | |
jabrena/plinth Use when you need to generate a checklist document with embedded commands inventory, following the embedded template exactly and producing INVENTORY-COMMANDS-JAVA.md in the project root. This should trigger for requests such as Create embedded commands inventory checklist; Generate INVENTORY-COMMANDS-JAVA.md; Use @001-commands-inventory; Inventory embedded Java project commands; List command files bundled for Java agents. Part of Plinth Toolkit | Skills | |
jabrena/plinth Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory; Inventory embedded Java agent definitions; List generated agent roles for Java development. Part of Plinth Toolkit | Skills | |
jabrena/plinth Use when you need to generate or improve Java project documentation — including README.md files, package-info.java files, and Javadoc enhancements — through a modular, step-based interactive process that adapts to your specific documentation needs. This should trigger for requests such as Improve the code with documentation; Apply documentation; Refactor the code with documentation; Generate README or developer documentation for a Java project; Document Java APIs architecture or project workflows. Part of Plinth Toolkit | Skills | |
jabrena/plinth Use when you need to install the embedded project commands into command directories (.github/commands, .claude/commands, .cursor/command, .codex/commands), selecting the destination interactively and copying the embedded command definitions from project assets. This should trigger for requests such as Install embedded commands; Bootstrap .cursor/command; Bootstrap .claude/commands; Copy project commands; Install project command suite. Part of Plinth Toolkit | Skills | |
jabrena/plinth Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should trigger for requests such as Review pom.xml to improve it; Apply Maven best practices to pom.xml; Improve Maven POM configuration; Review Maven dependency management and plugin configuration; Modernize Maven build conventions for a Java project. Part of Plinth Toolkit | Skills | |
jabrena/plinth Use when you need to set up, review, or improve Java integration tests — including generating a BaseIntegrationTest.java with WireMock for HTTP stubs, detecting HTTP client infrastructure from import signals, injecting service coordinates dynamically via System.setProperty(), creating WireMock JSON mapping files with bodyFileName, isolating stubs per test method, verifying HTTP interactions, or eliminating anti-patterns such as Mockito-mocked HTTP clients or globally registered WireMock stubs. This should trigger for requests such as Review Java code for integration tests; Apply best practices for integration tests in Java code; Write Java integration tests with real infrastructure boundaries; Improve Testcontainers integration tests for Java code; Review integration test setup and teardown in Java projects. Part of Plinth Toolkit | Skills | |
jabrena/plinth Use when building or reviewing core Quarkus applications with CDI beans and scopes, SmallRye Config and profiles, lifecycle, interceptors and events, virtual threads, and test-friendly design. This should trigger for requests such as Review Java code for Quarkus application structure and CDI; Apply best practices for Quarkus configuration and beans; Improve CDI interceptors, events, or programmatic injection in Quarkus; Add virtual-thread configuration or tune CDI lifecycle. ; Review Quarkus CDI bean lifecycle and configuration. Part of Plinth Toolkit | Skills | |
jabrena/plinth Use when you need to write or improve integration tests for Quarkus — including @QuarkusTest, Dev Services for automatic container provisioning, Testcontainers via QuarkusTestResourceLifecycleManager, WireMock for external HTTP stubs, @QuarkusIntegrationTest for black-box testing against packaged artifacts, REST Assured, data isolation strategies (@TestTransaction vs @BeforeEach cleanup), and Maven Surefire/Failsafe three-tier split (*Test, *IT, *AT). This should trigger for requests such as Add or improve integration tests in a Quarkus project; Configure Testcontainers or Dev Services for Quarkus tests; Add WireMock stubs for external HTTP dependencies in Quarkus integration tests; Set up @QuarkusIntegrationTest for packaged artifact or native binary testing; Fix test data isolation or configure Maven Surefire/Failsafe split. Part of Plinth Toolkit | Skills | |
jabrena/plinth Use when you need to design, review, or improve validation in Micronaut applications — including Bean Validation on @Controller methods, @Body @Valid, query/path parameter validation, @ConfigurationProperties validation, custom constraints, nested DTO validation, and ExceptionHandler mapping for constraint violations. This should trigger for requests such as Add validation support in Micronaut; Review Micronaut validation rules; Improve request validation in Micronaut REST APIs; Add custom validation constraints in Micronaut; Validate Micronaut configuration properties. Part of Plinth Toolkit | Skills | |
jabrena/plinth Use when you need to apply Java secure coding best practices — including validating untrusted inputs, defending against injection attacks with parameterized queries, minimizing attack surface via least privilege, applying strong cryptographic algorithms, handling exceptions securely without exposing sensitive data, managing secrets at runtime, avoiding unsafe deserialization, and encoding output to prevent XSS. This should trigger for requests such as Review Java code for secure coding; Find input validation risks in Java code; Review Java code for injection vulnerabilities; Improve secure error handling in Java services; Harden Java code against common security flaws. Part of Plinth Toolkit | Skills | |
drew-tessl/repo-schedules-test Reads recent project insights and events from the posthog MCP server (read-only) and writes what it found into a Markdown digest in this repo, then opens a pull request with that change. Runs unattended: it asks no questions and makes no writes to posthog. | Skills | |
drew-tessl/repo-schedules-test Pulls recently updated Linear issues (read-only) and writes them into a Markdown digest file in this repo, then opens a pull request with that change. Use to prove a scheduled run can reach Linear, turn what it read into a repo artifact, and publish it through a PR. Runs unattended: it asks no questions and makes no Linear writes. | Skills | |
ooooooooooooooooooop/ai_life_os Simulate high-stakes reasoning by modeling how top experts in the relevant domain would think, disagree, and converge on a decision. Use when users ask to role-play strongest minds, compare elite viewpoints, or ask: what would be a good group of people to explore X, and what would they say. Trigger for prompts like "think like world-class experts", "simulate top domain specialists", "role-play strongest domain people", and "use four-lens dialogue". | Skills | |
saski/arnesto Deep, pragmatic security review with OWASP and threat-modeling lens. Use when the user asks for security review, risk assessment, OWASP, or threat modeling. | Skills | |
saski/arnesto Design, organize, evaluate, benchmark, and improve portable Agent Skills. Use when creating a new skill, deciding whether a workflow deserves a skill, auditing a skill library, comparing a skill against baseline or prior versions, optimizing a skill description for better triggering, or retiring outdated skills across Claude, Codex, ChatGPT-compatible tools, and other Agent Skills-compatible environments. | Skills |
Can't find what you're looking for? Evaluate a missing skill.