CtrlK
BlogDocsLog inGet started
Tessl Logo

Discover

Discover and install skills, docs, and rules to enhance your AI agent's capabilities.

AllSkillsDocsRules
NameContainsScore

hono-api-scaffolder

jezweb/claude-skills

Scaffold Hono API routes for Cloudflare Workers. Produces route files, middleware, typed bindings, Zod validation, error handling, and API_ENDPOINTS.md documentation. Use after a project is set up with cloudflare-worker-builder or vite-flare-starter, when you need to add API routes, create endpoints, or generate API documentation.

Skills

69

coralogix/terraform-provider-coralogix

Use when tfgen generate must run before the management SDK is synced from a cx-management-apis PR (SDK_SYMBOL_MISSING for new contract fields). Builds a candidate SDK in a private GOMODCACHE.

Skills

69

rampstackco/claude-skills

How to author a content brief that actually guides a writer (human or AI) to produce a piece that ranks, converts, or both. Per-piece editorial brief: target keyword and cluster, search intent, audience and JTBD, heading structure, entity coverage for AEO/GEO, internal linking strategy, success criteria. The middle path between thin briefs (a keyword and a deadline) and thick briefs (a 4-page document nobody reads). Triggers on content brief, brief the writer, brief the article, brief authoring, content brief template, brief audit, per-piece brief, editorial brief, target keyword brief, search intent brief. Also triggers when briefing a human writer or an AI agent on a single content piece.

Skills

69

honeycombio/agent-skill

First principles of observability: wide events, high cardinality, the core analysis loop, events vs metrics vs logs, and how instrumentation connects to debugging. Trigger phrases: "what is observability", "why observability", "why Honeycomb", "events vs metrics vs logs", "why wide events", "what is high cardinality", "core analysis loop", "observability vs monitoring", "what is dimensionality", "explain observability".

Skills

69

anthropics/knowledge-work-plugins

Generate a daily or weekly digest of activity across all connected sources. Use when catching up after time away, starting the day and wanting a summary of mentions and action items, or reviewing a week's decisions and document updates grouped by project.

Skills

69

anthropics/knowledge-work-plugins

Identify, categorize, and prioritize technical debt. Trigger with "tech debt", "technical debt audit", "what should we refactor", "code health", or when the user asks about code quality, refactoring priorities, or maintenance backlog.

Skills

69

RHEcosystemAppEng/agentic-plugins

Execute governed job launches with check mode, approval gates, phased rollout, and rollback. Use when: - After execution-risk-analyzer has classified the execution risk - "Launch with check mode first", "Run the dry run" - "Execute the job" (after risk analysis) - "Rollback the failed job" NOT for: risk analysis (use execution-risk-analyzer first) or troubleshooting (use job-failure-analyzer).

Skills

69

microsoft/GitHub-Copilot-for-Azure

Review skill PRs with structured severity-rated feedback covering token budgets, routing conflicts, and repo conventions. WHEN: "review skill", "review skill PR", "review skill changes", "check skill quality", "skill PR feedback".

Skills

69

phuryn/pm-skills

Define a North Star Metric and 3-5 supporting input metrics that form a metrics constellation. Classify the business game (Attention, Transaction, Productivity) and validate against 7 criteria for an effective North Star. Use when choosing a North Star Metric, setting up a metrics framework, learning about the North Star Framework, or deciding what to measure.

Skills

69

phuryn/pm-skills

Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), solution, and release. Lean by default (about one to two pages), with a fuller spec on request. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

Skills

69

pmatos/skills

This skill should be used when the user asks to "plan this", "make a plan", "create an implementation plan", "how should I implement", "design the implementation", "plan the refactor", "plan the migration", "plan the feature", "break this down into steps", "implementation strategy", "deep plan", "thorough plan", or wants a thorough, multi-phase implementation plan with codebase exploration before writing any code.

Skills

69

openclaw/openclaw

Operate and troubleshoot the OpenClaw Control UI: navigate connected clients, organize sessions, build session dashboards, and handle direct or Tailscale-hosted Gateways.

Skills

69

marchatton/agent-skills

This skill should only be used when the user uses the word workflow and asks to shape a project from messy inputs into a de-risked, de-scoped shaped packet (brief, breadboard, risks, spikes) ready for wf-plan, with handoff/pickup boundaries to avoid context rot.

Skills

69

rohitg00/pro-workflow

Auto-grow a pro-workflow wiki by running a budget-capped BFS research loop over pluggable source fetchers (web, arXiv, GitHub). Each iteration pops a seed from the queue, fetches sources, drafts a wiki page, dedupes claims against existing pages, enqueues follow-up seeds. Halts on budget cap, depth cap, or convergence. Use when the user says "research <topic>", "grow the <slug> wiki", "auto-research", or wants a knowledge base that builds itself overnight.

Skills

69

ClawBio/ClawBio

Query metadata and download data from ArrayExpress, EMBL-EBI's functional genomics collection, now hosted inside BioStudies. Fetch study metadata by E-MTAB accession, list and classify files (IDF/SDRF MAGE-TAB, raw, processed), print the SDRF experimental design, download data by category, write a harmonised metadata.tsv, and build an nf-core/rnaseq or nf-core/scrnaseq samplesheet.csv from the SDRF.

Skills

69

huangkiki/dailypaper-skills

Discover trending GitHub repositories and research-related project updates. English triggers: "weekly GitHub trending", "daily GitHub trending", "monthly GitHub trending". 抓取 GitHub 上 star 涨得最快的项目(Trending 榜),打分标注是否与研究方向相关, 生成 Obsidian 笔记到 GitHubTrending 文件夹。默认周榜。 触发词:"GitHub 周榜"、"star 涨得最快"、"过去一周 GitHub 热门"、"GitHub trending"、 "看看这周 GitHub 上火了什么"、"GitHub 日榜"、"GitHub 月榜"

Skills

69

BankrBot/skills

Fund Venice AI inference (venice.ai) with staked DIEM on Base. Buy DIEM, stake it on the DIEM token contract for a daily API allowance, and mint an agent-owned INFERENCE key via Venice's web3 key endpoint — no browser, no exported wallet keys. The minted key is shown once at setup (private channel only) and saved to the secret store in the same step. Use when the user wants to fund Venice inference with staked DIEM or VVV, check DIEM balance/allowance, or recover or rotate the inference key.

Skills

69

dotnet/dotnet

Implementation details for the EF Core dotnet-ef CLI and tooling. Use when changing dotnet-ef commands, the ef wrapper, EFCore.Tools (PMC), or EFCore.Tasks MSBuild integration.

Skills

69

lyra81604/zhengxi-views

郑希观点库——基于易方达基金经理郑希 2012–2026 年全部公开观点原文语料,外加从语料蒸馏、有本人原话佐证的郑希投资方法的可溯源 research skill。能做: (1) 溯源问答——他怎么看 AI算力/光通信/新能源/半导体/ROE 等,引用其原话作答; (2) 讲解他的投资方法/框架/选股逻辑;(3) 前瞻应用——用他的方法分析当下任意主题/行业/个股,语料没谈过也能据框架推演; (4) 风格化点评——用他季报/手记的口吻写市场点评、季度展望; (5) 言行对照——用他全部基金真实数据(季度持仓/净值/业绩/规模/任职回报)核对"说的"与"买的",或答他的业绩/重仓/规模; (6) 全市场查询对比——内置约 2.7 万只基金列表,按需抓任意基金真实数据做查询或与郑希对比; (7) 郑希框架评分——给一只基金按他的方法打分(多像郑希会买的)。 When the user mentions 郑希/易方达郑希/zhengxi, asks his view on a sector/stock/theme, his 投资方法/框架/选股/风格/持仓/业绩/净值/规模, wants to apply his approach, a commentary 用郑希口吻, to check words vs holdings, or to look up/compare/score ANY China mutual fund (任意基金/某基金经理/同类对比/给基金打分)——use this skill, even if they don't say "skill", even if the topic isn't in his corpus (fall back to his method). 引用忠于原文、不杜撰;推演与原话区分。研究学习辅助,非投资建议。

Skills

69

tesslio/tessl-eval-demo

Implements a feature or bug fix test-first: write one failing test, run it and watch it fail, write the minimal code to pass, then refactor with the tests green. Use when a change alters code behavior: a new feature, a bug fix, or a behavior change, whether the request comes alone or through delivery-flow.

Skills

69

Can't find what you're looking for? Evaluate a missing skill.