Run any Skill in Manus with one click

ai-dev-tools-joke

Stars0

Forks1

UpdatedMarch 21, 2026 at 21:33

Tells AI dev tools themed jokes. THIS SKILL MUST be used any time the user asks for a joke about AI, dev tools, coding tools, evals, or AI development. Always invoke this skill before answering joke requests related to AI development tooling.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

gestrich

gestrich/AIDevTools

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Writers and AuthorsArts, Design, Entertainment, Sports, and Media Occupations·SOC 27-3043

SKILL.md

readonly

name	ai-dev-tools-joke
description	Tells AI dev tools themed jokes. THIS SKILL MUST be used any time the user asks for a joke about AI, dev tools, coding tools, evals, or AI development. Always invoke this skill before answering joke requests related to AI development tooling.
user-invocable	true

AI Dev Tools Joke

When invoked, respond with exactly this format:

AI DEV TOOLS JOKE:

Come up with a joke themed around AI development tools, evals, coding assistants, or AI-powered developer workflows. Always respond in the format above with no additional text.

More from this repository

same repository

claude-chain

gestrich/AIDevTools

Manages ClaudeChain automated PR chains. Use when working with claude-chain projects, listing open chain PRs, rebasing chain branches, triggering chain workflow runs, checking chain capacity, fetching workflow logs, creating new chains, or updating/editing an open chain PR locally.

2026-05-210

ai-dev-tools-debug

gestrich/AIDevTools

Debugging guide for AIDevTools (evals, plan runner, Mac app, PRRadar). Shows how to discover configured repositories, eval cases, artifact paths, plan storage, log files, and CLI commands for troubleshooting. Use this skill when: the user reports a bug, asks to check eval data, shares a screenshot of eval results or the Mac app, mentions a failing case, wants to inspect provider output, needs to debug plan generation or execution, or is debugging PRRadar behavior (pipeline output, rule evaluation, Mac app issues). Screenshots of the Mac app are a strong signal to invoke this skill — they mean the user wants you to reproduce or investigate using the CLI.

2026-04-180

ai-provider

gestrich/AIDevTools

Reference for where Claude and Codex provider data is stored on disk — session logs, raw output, thinking/reasoning availability, and format differences between the two providers. Use whenever investigating provider output, debugging missing thinking blocks, reading session history, or asking "where does X get stored for Claude vs Codex?"

2026-04-150

ai-dev-tools-ui-tests

gestrich/AIDevTools

Running, writing, and extracting screenshots from UI tests and interactive tests for the AIDevTools Mac app. Use this skill when: running XCUITests, capturing app screenshots, adding new screenshot tests, extracting images from .xcresult bundles, or using the interactive test runner (XCUITestControl) to programmatically drive the app UI.

2026-04-120

ai-dev-tools-composition-root

gestrich/AIDevTools

Guidance for this project's composition root pattern — how SharedCompositionRoot centralises shared service wiring, how the Mac app and CLI targets each have their own root that wraps it, and how platform-specific additions (models, git client, credentials) are layered on top. Use this when adding new shared services, creating a new CLI command that needs services, modifying how providers or credentials are wired, reviewing code that constructs services outside a composition root, or any time someone asks how dependency wiring works in this project.

2026-04-110

ai-dev-tools-configuration-architecture

gestrich/AIDevTools

Guide for adding, modifying, or reviewing configuration in this Swift app. Use when adding credentials or API keys, creating a new config file, adding a ServicePath case, setting up a service that reads settings, wiring configuration through the Apps layer, reviewing whether config is injected correctly (resolved values vs raw services), asking 'where should this config go?', or adding per-repo feature settings. Also use when working with SecureSettingsService, CredentialResolver, SettingsService, DataPathsService, or RepositoryConfiguration anywhere in the codebase.

2026-04-100