CtrlK
BlogDocsLog inGet started
Tessl Logo

Discover skills

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

AllSkillsDocsRules
NameContainsScore

tdg-personal/article-writing

v0.1.0

Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.

Contains:

article-writing

Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.

Skills

69

Proactively searches the Tessl registry for best-practice tiles before starting work that involves frameworks, libraries, or technologies where conventions matter. Triggers automatically when about to write tests, configure CI, set up auth, handle errors, design APIs, write database migrations, configure Docker, set up linting, or work with any framework or technology. Also triggers when the agent thinks "I should check if there are established best practices for this." Do NOT use for trivial edits, renaming variables, or tasks that don't involve technology-specific conventions. Requires Tessl MCP tools: search and install.

Contains:

best-practice-scout

MANDATORY first step before writing any code that uses a framework, library, or technology. Searches the Tessl registry for best-practice tiles and installs them before implementation begins. MUST be invoked before: building a new app or feature, writing tests, configuring CI, setting up auth, designing APIs, database work, Docker setup, linting config, or any task involving React, Express, Next.js, TypeScript patterns, Playwright, SQLite, or other technologies. Use when the user says "build", "create", "implement", "set up", "configure", "write tests", or starts any greenfield project. Do NOT use for trivial edits or renaming variables. Requires Tessl MCP tools: search and install.

Skills

69

Apply this skill when designing, building, or reviewing API routes, Server Actions, or data fetching patterns in a Next.js + TypeScript + Drizzle application. Triggers on requests like "create an API endpoint", "add a server action", "design the API", "add pagination", "handle this request", "validate query params", or any time you are building the boundary between client and server. Use proactively — all API design decisions should follow these patterns.

Contains:

api-design

Apply this skill when designing, building, or reviewing API routes, Server Actions, or data fetching patterns in a Next.js + TypeScript + Drizzle application. Triggers on requests like "create an API endpoint", "add a server action", "design the API", "add pagination", "handle this request", "validate query params", or any time you are building the boundary between client and server. Use proactively — all API design decisions should follow these patterns.

Skills

69

Apply this skill when writing, reviewing, or planning tests for a Next.js + TypeScript + Drizzle application using Vitest, React Testing Library, MSW, and Playwright. Triggers on requests like "write tests for", "add test coverage", "test this component", "test this hook", "test this API route", "add E2E tests", "is this testable", or any time you are building features that need verification. Use proactively — all new features should include tests.

Contains:

testing

Apply this skill when writing, reviewing, or planning tests for a Next.js + TypeScript + Drizzle application using Vitest, React Testing Library, MSW, and Playwright. Triggers on requests like "write tests for", "add test coverage", "test this component", "test this hook", "test this API route", "add E2E tests", "is this testable", or any time you are building features that need verification. Use proactively — all new features should include tests.

Skills

69

Apply this skill when writing, reviewing, or refactoring any code in a React + TypeScript + Tailwind + shadcn + Drizzle project. Triggers on requests like "review this code", "refactor this component", "is this good practice", "write a hook for", "clean this up", "add types to", "write a form", or any time you are producing code that should meet production standards. Use proactively — all generated code should conform to these standards without being asked.

Contains:

code-quality

Apply this skill when writing, reviewing, or refactoring any code in a React + TypeScript + Tailwind + shadcn + Drizzle project. Triggers on requests like "review this code", "refactor this component", "is this good practice", "write a hook for", "clean this up", "add types to", "write a form", or any time you are producing code that should meet production standards. Use proactively — all generated code should conform to these standards without being asked.

Skills

69

Apply this skill when building, optimising, or reviewing components, data fetching, or database queries in a Next.js App Router + TypeScript + Tailwind + shadcn + Drizzle application where performance matters. Triggers on requests like "optimise this", "this is slow", "reduce re-renders", "improve load time", "this list is laggy", "bundle is too large", "slow query", or any time you are building features that involve large lists, frequent updates, heavy computations, or significant data volumes. Use proactively for anything rendering more than ~50 items or running on every keystroke.

Contains:

performance

Apply this skill when building, optimising, or reviewing components, data fetching, or database queries in a Next.js App Router + TypeScript + Tailwind + shadcn + Drizzle application where performance matters. Triggers on requests like "optimise this", "this is slow", "reduce re-renders", "improve load time", "this list is laggy", "bundle is too large", "slow query", or any time you are building features that involve large lists, frequent updates, heavy computations, or significant data volumes. Use proactively for anything rendering more than ~50 items or running on every keystroke.

Skills

69

All AEM as a Cloud Service skills: component development, Workflow model design, development, triggering, launchers, debugging, and triaging, Dispatcher config authoring, advisory, incident response, performance tuning, and security hardening, Rapid Development Environment (RDE) deployment, log inspection, snapshots, and troubleshooting via `aio aem rde`, Jackrabbit Oak query/index tuning (property, Lucene index definitions), and extracting/inventorying JCR queries (XPath, SQL2, QueryBuilder) across a codebase.

Contains:

aem-rde

[BETA] Expert assistance for the Adobe I/O CLI plugin `@adobe/aio-cli-plugin-aem-rde` — the `aio aem rde` / `aio aem:rde` command tree used to deploy, inspect, log-tail, snapshot, and troubleshoot AEM Rapid Development Environments (RDEs). Activate ONLY when the user explicitly references RDE concepts: 'AEM RDE', 'Rapid Development Environment', `aio aem rde`, `aio aem:rde`, `aem-rde`, RDE snapshots, RDE deploy/install, `rde install`, `rde inspect`, `rde status`, `rde history`, `rde reset`, the `@adobe/aio-cli-plugin-aem-rde` package, or Cloud Manager program/environment configuration that is specifically for an RDE environment. Do NOT activate on generic AEMaaCS phrases like 'deploy to AEM Cloud', 'push my bundle', 'tail the publish log', 'cloud sandbox', or unqualified 'dispatcher-config / frontend / env-config deployments' — those belong to Cloud Manager pipelines, not RDE. This skill is in beta. Verify all outputs before applying them to production projects.

aem-workflow

Single entry point for all AEM as a Cloud Service Workflow skills. Covers workflow model design, custom process step and participant chooser development, launcher configuration, workflow triggering, and production support including debugging stuck/failed workflows, triaging incidents with Cloud Manager logs, thread pool analysis, and Sling Job diagnostics for the Granite Workflow Engine.

code-assessment

Detect, review, and fix code-quality, correctness, and security issues in an AEM as a Cloud Service project — locally, with no external services or network calls. Use whenever a user wants to check, review, assess, audit, scan, modernize, upgrade, or fix AEM Java, Sling Models, OSGi, or Maven code — for example: "check my Sling Models are implemented correctly", "review my @Inject usage", "are my Maven dependencies up to date", "scan this AEM project for issues", "can a cookie skip my login captcha", "calls to an external API hang", or "fix code-quality problems". Name the files to assess, or ask it to scan the repo; it detects issues, plans, and — only when you ask — applies surgical edits on a branch or in place, then verifies with mvn compile. It recognises the intent and handles each issue type itself, reporting anything it cannot yet fix.

Skills

69

debugging-strategies

Dicklesworthstone/pi_agent_rust

Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.

Skills

69

1.01x

github/awesome-copilot

Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.

Skills

69

1.12x

administrakt0r/AI-Agents-Safe-Coding-Skills

Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices

Skills

69

1.11x

administrakt0r/AI-Agents-Safe-Coding-Skills

Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices

Skills

69

1.11x

administrakt0r/AI-Agents-Safe-Coding-Skills

Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices

Skills

69

1.11x

NeverSight/learn-skills.dev

DEPRECATED: Use testing-best-practices instead. This skill has been retired.

Skills

69

1.30x

davepoon/buildwithclaude

Automate Make (Integromat) tasks via Rube MCP (Composio): operations, enums, language and timezone lookups. Always search tools first for current schemas.

Skills

69

1.07x

deepgram/dglabs-deepclaw

Control Eight Sleep pods (status, temperature, alarms, schedules).

Skills

69

2.07x

attilaczudor/Test

Control Eight Sleep pods (status, temperature, alarms, schedules).

Skills

69

2.07x

Hung-Reo/hungreo-openclaw

Control Eight Sleep pods (status, temperature, alarms, schedules).

Skills

69

2.07x

wu-yc/LabClaw

Biological data toolkit. Sequence analysis, alignments, phylogenetic trees, diversity metrics (alpha/beta, UniFrac), ordination (PCoA), PERMANOVA, FASTA/Newick I/O, for microbiome analysis.

Skills

69

2.86x

Assurance guidance for verification, technical review, review fixes, and safe delivery handoff.

Contains:

finishing-a-development-branch

Verify tests pass, then present the integration options for a finished branch — merge locally, push and open a pull request, or keep it as-is — execute the choice, and clean up the worktree safely. This is the internal integration stage of the delivery-flow workflow. Use it only after implementation is verified and only when the user has authorized an integration decision, for example by saying "finish this branch", "merge my work", or "open a PR" — never activate it directly for an unrelated standalone request.

receiving-code-review

Evaluate code review feedback on its technical merits, verify each suggestion against the codebase, then implement the fixes that hold up and push back with reasoning on the ones that don't. This is the internal review-fix stage of the delivery-flow workflow, run when delivery-flow receives feedback from a reviewer. It is not a standalone entry point, so do not activate it directly for a one-off "address this review comment" or "respond to PR feedback" request; use delivery-flow for those instead.

requesting-code-review

Dispatch a code-reviewer subagent with precisely scoped context (git SHAs, task description, requirements) to review a diff and return Critical, Important, and Minor findings. Use after delivery-flow finishes implementing and verifying a task, before merging to main. This is the internal code-review stage of the delivery-flow workflow. It is not a standalone entry point, so do not activate it directly for a one-off "review this PR" or "review my code" request; use delivery-flow for those instead.

Skills

69

Use when writing Python code with `axllm` for agent memory, recall callbacks, dynamic skill discovery, loaded-skill state, and used-skill tracking.

Skills

69

1.63x

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