Discover and install skills to enhance your AI agent's capabilities.
| Name | Contains | Score |
|---|---|---|
Kotlin/coroutines patterns for driving rate-limited IoT actuators from real-time producers: debounce controller, target quantization, bottom-up progress-bar rendering. Contains: debounce-controller-kotlin One-coroutine-per-device debounce controller for rate-limited IoT APIs in Kotlin. Min-interval throttle, 2-tick stability filter, send-latest semantics. Min-interval is 0.2s for LAN devices, 1.2s for cloud APIs. Dispatches on Dispatchers.IO. Use when a real-time producer (camera loop, sensor feed, Flow<T>) drives a cloud or LAN IoT device that can't keep up with per-frame updates, or when you see flicker / HTTP 429 errors from hammering an actuator. render-progress-bar-kotlin Render a segmented LED progress bar that fills bottom-up with red/yellow/green gradient — thermometer pattern, not falling-bar. Handles top-indexed hardware (where segment[0] is physically at the top) and bottom-indexed hardware. Use when wiring a quantised level (0..N) into an LED bar, especially Govee H6056, Hue Lightstrip, or similar segmented devices where fill direction and gradient matter. target-quantization-kotlin Discretise continuous producer signals (Float, Double) into Int targets so the debounce controller's stability filter can actually commit. Without quantization, a noisy 0.42-vs-0.43-vs-0.42 signal blocks every commit and the actuator stays dark. Use when wiring a continuous producer (confidence score, sensor reading, audio level) into a debounce controller, or debugging "I call submit() but onApply() never fires". | SkillsRules | |
v0.2.4 Research toolkit for triaging academic papers and GitHub projects. Triage papers and tools, reproduce benchmark claims, search Google Scholar, Semantic Scholar, PubMed, or Sci-Hub, and extract structured data from scientific PDFs. Contains: google-scholar-search Search Google Scholar for academic papers and author profiles. Use when discovering papers to triage — by keyword, author, or year range. Returns titles, authors, abstracts, and links. Triggers: search papers, find papers, google scholar, search scholar, find author, author profile, literature search, paper discovery, search academic literature. pubmed-search Search and analyze biomedical literature from PubMed using the free E-utilities API. Use when researching medical topics, discovering clinical papers, fetching article metadata by PMID, performing deep paper analysis, or downloading open-access PDFs from PubMed Central. Triggers: pubmed search, search biomedical literature, find medical papers, PMID lookup, pubmed metadata, clinical literature search, biomedical research, life sciences papers, PMC download, ncbi search. reproduce-benchmark Reproduce and verify the benchmark claims of a tool or paper already triaged in the research repo. Locates the benchmark harness, runs it, and records verified vs. reported figures in benchmarks/sources/{slug}-repro.md. Triggers: reproduce benchmark, verify claims, run benchmark, check benchmark, benchmark reproduction, verify numbers. sci-data-extractor Extract structured data from scientific literature PDFs using AI-powered OCR and LLM analysis. Supports enzyme kinetics, experimental results, and literature review templates. Use when researchers need to parse tables, charts, or text from paper PDFs into Markdown or CSV. Triggers: extract data from PDF, scientific data extraction, parse paper tables, enzyme kinetics extraction, batch PDF extraction, literature data, research data from paper, OCR scientific paper, convert PDF to structured data. sci-hub-search Search and download academic papers through Sci-Hub by DOI, title, or keyword. Supports PDF download, metadata extraction, and automatic mirror detection via CrossRef integration. Use when a paper is behind a paywall and you have the DOI or title. Triggers: sci-hub, download paper, fetch paper, academic paper download, paper by DOI, paper access, paywall bypass, retrieve paper, get full text, paper download. semantic-scholar-search Search Semantic Scholar for academic papers, fetch paper details by ID or DOI, retrieve author profiles, and analyse citation graphs. Preferred over google-scholar-search — uses the official API with no scraping. Triggers: search papers, find papers, semantic scholar, paper details, paper by DOI, paper by ID, author profile, citation analysis, references, literature search, paper discovery. triage-paper Triage an academic paper into a structured reference summary for the research repo. Use when given an arxiv ID, arxiv URL, DOI, or paper PDF. Creates references/{slug}.md; adds REVIEWED.md entry and REFERENCE_INDEX.md row. Triggers: triage paper, add paper, analyse paper, review paper, literature review, survey paper, benchmark paper, deep dive paper, arxiv, DOI. triage-tool Triage a tool or library into a structured reference summary for the research repo. Use when given a GitHub URL, npm package, PyPI package, or CLI tool name. Creates references/{slug}.md with architecture overview and scope assessment; adds REVIEWED.md entry and REFERENCE_INDEX.md row. Triggers: triage tool, add tool, analyse tool, GitHub project, npm package, PyPI package, library, framework, CLI tool, MCP server, open source project. | Skills | |
Implementation guidance for executing plans with test-driven development and systematic debugging. Contains: executing-plans Executes a written multi-step implementation plan end to end - loads the plan, reviews it critically for gaps, works through each task with its verification steps, and reports when everything is done. This is the execution stage inside the delivery-flow workflow, entered by requests like "implement this plan", "run the plan", "execute the plan", or "work through these tasks" once delivery-flow has produced a written plan. Do not activate directly for a standalone request that has not gone through delivery-flow first. systematic-debugging Investigates a test failure, bug, or unexpected behavior to find its root cause before proposing any fix - reproduce the issue, trace the data flow, form and test one hypothesis at a time, then implement and verify the fix. This is the debugging stage inside the delivery-flow workflow, entered by requests like "debug this failure", "why is this test failing", "find the root cause", or "this bug keeps coming back" once delivery-flow has handed off a bug. Do not activate directly for a standalone bug report that has not gone through delivery-flow first. test-driven-development Implements a feature or bug fix test-first - write one failing test, watch it fail, write the minimal code to pass, then refactor with tests green. This is the implementation stage inside the delivery-flow workflow, entered by requests like "implement this feature", "fix this bug", "write the code for this", or "add the tests and implement it" once delivery-flow is driving the change. Do not activate directly for a standalone request that has not gone through delivery-flow first. | Skills | |
v0.3.1 Comprehensive Kubernetes toolkit for YAML generation, validation, and cluster debugging Contains: k8s-debug Inspect pod logs, analyze resource quotas, trace network policies, check deployment rollout status, and run cluster health checks for Kubernetes. Use this skill when diagnosing Kubernetes cluster issues, debugging failing pods, investigating network connectivity problems, analyzing resource usage, troubleshooting deployments, or performing cluster health checks. k8s-yaml-generator Comprehensive toolkit for generating, validating, and managing Kubernetes YAML resources. Use this skill when creating Kubernetes manifests (Deployments, Services, ConfigMaps, StatefulSets, etc.), working with Custom Resource Definitions (CRDs), or generating production-ready K8s configurations. k8s-yaml-validator Comprehensive toolkit for validating, linting, and testing Kubernetes YAML resources. Use this skill when validating Kubernetes manifests, debugging YAML syntax errors, performing dry-run tests on clusters, or working with Custom Resource Definitions (CRDs) that require documentation lookup. | Skills | |
arwei944/codeg You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. | Skills | |
valeriibeck-star/claude-skills You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. | Skills | |
foryourhealth111-pixel/Vibe-Skills Personalized coding tutorials that build on your existing knowledge and use your actual codebase for examples. Creates a persistent learning trail that compounds over time using the power of AI, spaced repetition and quizes. | Skills | |
openai/plugins Deploying Expo apps to iOS App Store, Android Play Store, web hosting, and API routes | Skills | |
Dicklesworthstone/pi_agent_rust Configure secure, high-performance connectivity between on-premises infrastructure and cloud platforms using VPN and dedicated connections. Use when building hybrid cloud architectures, connecting data centers to cloud, or implementing secure cross-premises networking. | Skills | |
administrakt0r/AI-Agents-Safe-Coding-Skills Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure. | Skills | |
administrakt0r/AI-Agents-Safe-Coding-Skills Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure. | Skills | |
administrakt0r/AI-Agents-Safe-Coding-Skills Expert C4 Code-level documentation specialist. Analyzes code directories to create comprehensive C4 code-level documentation including function signatures, arguments, dependencies, and code structure. | Skills | |
v0.24.1 Set up, understand, and change a Tessl factory on a repository: pick automations that fit how you work, such as shipping tickets as pull requests, answering reviews and fixing checks on those pull requests, code review, and scheduled jobs; prepare the repository for agents; write issues for the factory to build; then see what the factory has done, find out why a run failed or never started, and change or extend it. Contains: change-factory Change or extend a Tessl factory that is already set up on this repository, and suggest what to add next. Use when someone wants to let a teammate start runs, change the model an automation uses, change what an automation does, change how Code Review behaves, stop or remove an automation, update the setup hook, change what the cloud environment can access, add another automation, set up Learn from past work so the factory learns from its mistakes, act on its findings, or asks what they should add to their factory. check-cloud-setup Run a branch's setup hook on a Tessl cloud machine and report its output and what the machine then has, so factory setup can confirm the hook works in the cloud before it goes live. Use when factory setup launches a cloud run to check a setup hook. create-github-issue Write and file a GitHub issue for the Tessl factory to turn into a pull request, with the person's own GitHub account. Use when someone wants Tessl to work on something in a repository whose factory takes GitHub issues, wants a task split into issues the factory builds in order, or asks how to write an issue for Tessl. create-linear-issue Write and file a Linear issue for the Tessl factory to turn into a pull request, with the person's own Linear access, and delegate it to Tessl. Use when someone wants Tessl to work on something in a repository whose factory takes Linear issues, wants a task split into issues the factory builds in order, or asks how to write an issue for Tessl. factory-setup Set up a Tessl factory on a repository: Tessl agents that turn tickets into pull requests, answer reviews and fix checks on them, and review every pull request. Use when someone wants Tessl agents to do work in their repo, or asks what a factory is. To explain or change a factory that exists, use the understand-factory and change-factory skills. prepare-repo Prepare an existing repository so Tessl agents and Tessl Code Review work well in it: better agent context, verifiers, Code Review lenses, and lint rules drawn from how the team already works. Use when someone wants agents to make fewer mistakes in their repo, wants to prepare or improve their repo for agents, or wants to turn recurring review feedback into checks. understand-factory Explain what a Tessl factory on this repository has done and is doing, and why something went wrong. Use when someone asks what their factory, automations, or loops have been doing, what happened on an issue or pull request Tessl worked on, why a run failed or nothing happened after they labeled an issue or left a review, whether anything is stuck or needs them, or how many credits it has used. write-factory-skill Write or rewrite a skill used in a Tessl factory: a new skill for an automation, a copy of a published factory skill kept in the repository, or a skill that takes over work a script, a runbook or an earlier skill does today. Use when drafting such a skill, rewriting one that has grown into a numbered procedure, or checking one before it merges. | Skills | |
github/awesome-copilot Suggest relevant GitHub Copilot instruction files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing instructions in this repository, and identifying outdated instructions that need updates. | Skills | |
davepoon/buildwithclaude Automate Coda tasks via Rube MCP (Composio): manage docs, pages, tables, rows, formulas, permissions, and publishing. Always search tools first for current schemas. | Skills | |
Consensys-Incorporated/ocap-kernel How to add entries to the glossary | Skills | |
v0.1.0 Agent kit for working on canonical/chisel-releases. Cross-agent skills + scripts for authoring and reviewing chisel slice definition files. Contains: chisel-releases Author or review chisel slice definition files (SDFs) against canonical/chisel-releases. Command-per-file architecture, portable across claude code, pi, opencode, copilot, and codex. Commands: write-slice (author + test + commit), review-slice (read-only review). Use when user says "add slice", "write a chisel slice", "review slices/<pkg>.yaml", or works inside a canonical/chisel-releases checkout. mason Entry point for the mason agent kit. Routes a plain-language request to the right mason skill, or prints usage when the intent is unclear. Use when user runs /mason (with a request or bare), says "mason help", or "what can mason do". | Skills | |
Complete GitHub Actions toolkit with generation and validation capabilities for workflows, custom actions, and CI/CD configurations Contains: github-actions-generator Generates production-ready GitHub Actions workflows, custom actions, and CI/CD configurations following security and performance standards. Creates CI/CD pipelines, test workflows, deployment configurations, matrix builds, caching strategies, composite actions, Docker actions, JavaScript actions, and reusable workflows. Use when creating or scaffolding GHA resources, writing .github/workflows YAML files, setting up build automation, implementing deployment pipelines, adding security scanning, or building reusable actions — including triggers like 'create a workflow', 'build a pipeline', 'add CI', 'set up GHA', or 'generate a YAML workflow'. github-actions-validator Comprehensive toolkit for validating, linting, and testing GitHub Actions workflow files, custom local actions, and public actions. Use this skill when working with GitHub Actions YAML files (.github/workflows/*.yml), validating workflow syntax, testing workflow execution with act, or debugging workflow issues. | Skills | |
Complete terraform toolkit with generation and validation capabilities Contains: terraform-generator Generate Terraform modules, configure providers, define variables and outputs, set up remote state backends, and write production-ready HCL (.tf files) following current standards. Use when creating new Terraform resources, building Terraform projects, writing infrastructure as code (IaC), scaffolding AWS/Azure/GCP cloud infrastructure, working with terraform plan/apply workflows, or structuring multi-environment configurations. terraform-validator Comprehensive toolkit for validating, linting, testing, and automating Terraform configurations and HCL files. Use this skill when working with Terraform files (.tf, .tfvars), validating infrastructure-as-code, debugging Terraform configurations, performing dry-run testing with terraform plan, or working with custom providers and modules. | Skills | |
Skills for building AEM Edge Delivery Services sites — site creation, block development, content modeling, code review, testing, and page import. Contains: aem-block-library Use when a new or changed AEM Edge Delivery Services block needs an entry in the block library that authors use to find and insert it: the Experience Workspace (formerly DA, Document Authoring) library or the Sidekick Library for Word and Google Docs projects. Covers finding the project's library, the block page, variants, the sheet row, library metadata and the steps that happen outside the repo. For tests that run against the library page use testing-blocks. aem-cli Use this when running or troubleshooting the local Edge Delivery dev server or the Adobe AEM CLI (@adobe/aem-cli, formerly helix-cli; `aem up`, `aem content`, `aem import`). Covers starting `aem up` and its port (git worktrees, a port already in use), serving local test pages from `./content/`, cloning da.live content locally with `aem content clone` to preview, inspect or edit it and pushing edits back, `aem up` failures (cert errors, proxy 404s, local pages not found), .env / AEM_* configuration, HTTPS, installing or upgrading the CLI, and the importer server. For da.live content-format rules or the DA Source API use da-content; for writing EDS block code use content-driven-development. aem-layout-view Use when block or site code of an AEM Edge Delivery Services project authored in Experience Workspace (EW, formerly DA, Document Authoring) must stay editable in layout view, the WYSIWYG page editor that renders the page with the site's own code: authors can't edit a block's text or images, blocks duplicate or misbehave after edits, a request fails only in layout view, or a branch needs testing there. Not for the Universal Editor (ue-component-model) or projects authored in Word or Google Docs. authoring-analysis Use this when the page-import pipeline needs to determine the authoring approach (default content vs blocks) for scraped content before generating import HTML for AEM Edge Delivery Services. Covers validating block selection and section styling for import/migration. Do not invoke directly — called by page-import as a pipeline step. block-collection-and-party Use this when you are starting AEM Edge Delivery Services (EDS, Franklin, Helix) development and want an existing reference to build from, such as a block, build tool, code snippet, integration pattern, or plugin. Searches the Block Collection and Block Party repositories, matches candidates against the need, and returns a suitable starting point to clone or adapt. brand-setup Use when a fresh AEM Edge Delivery Services boilerplate project should take on the brand basics of an existing website being migrated to EDS — colors, body and heading fonts, font sizes, header height, favicon and logo. Triggers include "set up the brand from <site>", "match the source site's look", "apply the client's fonts and colors", "use their favicon and logo". Not for projects whose styles were already customized, and not for full design-system extraction (spacing scales, components, motifs). building-blocks Use this before writing or changing AEM Edge Delivery Services (EDS, Franklin, Helix) block or site code: a block's `decorate(block)`, block CSS and variants, `scripts.js` loading phases (eager, lazy, delayed), images, fragments, and LCP or performance fixes. EDS conventions don't always match standard front-end practice because of its architecture and page-loading model, and the boilerplate keeps evolving past model training cutoffs, so check here rather than relying on memory. For new blocks or changes to the authored structure, start with content-driven-development. code-review Use when asked to review AEM Edge Delivery Services (EDS, Franklin, Helix) code: a pull request, branch, diff, or your own changes before opening a PR. Lists the EDS-specific checks to apply on top of normal code review. content-driven-development Use this when building a new AEM Edge Delivery Services (EDS, Franklin, Helix) block, or when changing what authors put into an existing block (new rows or cells, author-selectable variants, a different table structure). Runs the content-first workflow: find or create test content before code, design an author-friendly content model, and validate against that content. For code-only changes that keep the authored structure (CSS fixes, JavaScript bugs, scripts.js, performance, lint) use building-blocks directly. content-modeling Use this to decide what authors type for an AEM Edge Delivery Services (EDS) block, in any editor (Word, Google Docs, Experience Workspace, Universal Editor): the table layout (rows, cells, columns), variants, per-item options such as featured, lists, tabular data, forms, and whether something should be a block at all. Also use it to review or simplify a block's author-facing structure, before writing block code for a new block or a changed structure. Not for decorate JS or CSS once the model is set. create-site Use this when a user wants to create a brand-new AEM Edge Delivery site from scratch: no GitHub repository or content exists yet, or a repo made from the boilerplate template is not connected to content yet. Triggers include 'set up a new site', 'create a new EDS project', 'onboard a new site'. Covers creating the repo from the boilerplate, installing aem-code-sync, choosing the content store (DA at admin.da.live or Source Bus at api.aem.live), seeding nav, footer and homepage, and returning a live preview URL. For importing existing pages use page-import; for blocks on an existing site use content-driven-development. da-auth Use this to obtain, reuse, refresh or troubleshoot Adobe IMS authentication for Experience Workspace (formerly DA) content APIs: admin.da.live (DA) or api.aem.live (Source Bus). Use before pushing HTML content, listing documents or triggering a preview when no credential is known to work for that API, or for 401/403 (Unauthorized/Forbidden) and authentication checks where status 200 is insufficient. Not for choosing a content store or planning content changes when authentication already works. da-content Use before writing, fixing or answering questions about the HTML of pages that authors edit in Experience Workspace / DA (da.live), including hand-written sample pages for local testing. The pipeline silently drops or rewrites markup in ways that are not guessable, so check here first when a generated page previews empty, loses its metadata, icons, Section Metadata style or block, shows about:error images, turns a table into a block, loses span classes or bold in block cells, or has its links rewritten; when uploading pages or media to the DA source API or the Source Bus API at api.aem.live (200 but nothing written, SVG over 40 KB returns 409); or when you need to see how the pipeline read a page. Not for block JS/CSS (building-blocks), tokens (da-auth) or the aem CLI (aem-cli). figma-to-content Use this to turn a Figma design into an AEM Edge Delivery Services (EDS / AEM / Franklin / Helix) content page in Document Authoring (DA, da.live). Triggers: "build this Figma frame in EDS", "turn this Figma design into a DA page", "publish this design to da.live", or providing a figma.com URL for a page. Reads the frame (and any annotations) via a Figma MCP, resolves each section to an existing block, a new isolated block, or default content (inferred against the project's existing blocks and confirmed with you, or read from annotations when the frame happens to have them), generates DA-compliant body-fragment HTML, and deploys via the DA Source API + preview. find-test-content Use this when you need real pages that already use a specific block or block variant on an AEM Edge Delivery Services site (local dev, `.aem.page` or `.aem.live`): to audit usage before removing, renaming or restyling a block, or to find real pages to regression-test a change when the block has no library test page. For creating or cloning local test pages use aem-cli; for importing an external URL use page-import; for searching Adobe's Block Collection or Block Party use block-collection-and-party. generate-import-html Use this when the page-import pipeline needs to produce structured HTML from authoring analysis for AEM Edge Delivery Services. Covers building section structure, applying block tables, handling metadata, and managing the images folder. Do not invoke directly — called by page-import as a pipeline step. identify-page-structure Use this when the page-import pipeline needs to identify section boundaries and content sequences within a scraped webpage for AEM Edge Delivery Services import. Outputs an ordered list of sections, the content sequence within each section, and candidate block-type annotations via two-level analysis (sections, then sequences per section). Do not invoke directly — called by page-import as a pipeline step. migrate-header Use this when rebuilding an existing website's header as the header block of an AEM Edge Delivery Services project so that it matches the source 1:1 — closed at every width, with every menu open, with the mobile menu open, and while scrolling. Captures the source header with the web CLI (`web header capture`), installs a configurable header block and its nav document, then runs a ladder of `web header check` commands against the live source until nothing differs. Triggers include "migrate the header of <site>", "rebuild this header in EDS", "header 1:1 with the source". For whole pages use page-import; to keep the source DOM as it is use snowflake; for other blocks use content-driven-development. page-decomposition Use this when the page-import pipeline needs to analyze the content sequences within a single section and describe them neutrally for AEM Edge Delivery Services. Covers identifying breaking points between default content and blocks, one section at a time. Do not invoke directly — called by page-import per section. page-import Use this when importing or migrating a single webpage from any URL into canonical EDS block format — structured HTML that authors edit in DA — including when the request uses terms like migrate, migration, or migrating. Covers scraping the page, analyzing structure, mapping to existing blocks, and generating HTML for immediate local preview. Use the snowflake skill instead when the user wants to preserve the original DOM byte-for-byte (static-to-EDS overlay); for building new blocks from scratch use content-driven-development. preview-import Use this when you need to preview and verify content you imported into a local AEM Edge Delivery Services (EDS, Franklin, Helix) dev server on localhost. Starts the dev server against the imported HTML, checks block rendering, inspects DOM structure, compares against the original page, and troubleshoots broken references and 404s. scrape-webpage Use this when the page-import pipeline needs to fetch a source webpage and prepare it for import/migration to AEM Edge Delivery Services. Covers scraping content, extracting metadata, downloading images, and returning analysis JSON with paths, metadata, cleaned HTML, and local images. Do not invoke directly — called by page-import as a pipeline step. slicc-handoff Use this when the user asks to continue work in the SLICC browser agent or to install a skill into SLICC, for example "handoff to slicc", "move to the browser", "test in the browser", "install this skill in slicc", or "upskill slicc with this repo". Covers handing off the current task to the SLICC browser agent and installing a new skill into SLICC from a GitHub repo. snowflake Use this when converting an AI-generated static HTML page (Stardust, Mobirise, Relume, Lovable, v0, Figma-derived, etc.) into an Edge Delivery Services page while preserving the original design and making content authorable in Document Authoring — triggers include "convert this page to EDS", "static-to-EDS overlay", "convert to EDS blocks", "next experimentation", "next run", "start run", or providing a source URL to make editable in DA. Covers two modes — page-level (overlay template with slot markers) and block-level (each section becomes an independent EDS block). For canonical EDS block-rewrite migrations use page-import instead. testing-blocks Use before writing unit or Playwright E2E tests for an AEM Edge Delivery Services block or script, when deciding what tests a block change needs, or when validating block, script or style changes in a browser before a pull request. EDS block testing has non-obvious conventions (how to locate elements without breaking on author edits, library page vs drafts, analytics assertions, no-framework-addition rule, and waiting on decoration), so check here first. Not for implementing block code (building-blocks) or PR review comments (code-review). ue-component-model Use this to set up an AEM Edge Delivery Services block for the Universal Editor in an AEM-authoring (xwalk) project: the block's component definition, model (properties-panel fields) and filters in `blocks/<name>/_<name>.json`, adding it to the editor's add menu, option fields, multi-value fields, and tabs or containers. Also use it to fix a block missing from the add menu, or edits to component-definition.json, component-models.json or component-filters.json that disappear (those files are generated by build:json). Use content-modeling first to decide the block's structure; this skill only maps that structure to Universal Editor fields. Not for document-based authoring (Word, Google Docs, DA) or for decorate JS and CSS. | Skills |
Can't find what you're looking for? Evaluate a missing skill.