Topic: ai
10,359 skills in this topic.
-
himalaya
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).
openclaw/openclaw 355,710
-
openai-whisper
Local speech-to-text with the Whisper CLI (no API key).
openclaw/openclaw 355,710
-
xurl
A CLI tool for making authenticated requests to the X (Twitter) API. Use this skill when you need to post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, or interact with any X API v2 endpoint.
openclaw/openclaw 355,710
-
octave-compression
Specialized workflow for transforming verbose natural language into semantic OCTAVE (Olympian Common Text And Vocabulary Engine) structures. REQUIRES octave-literacy to be loaded first
elevanaltd/octave-mcp 45
-
octave-literacy
Fundamental reading and writing capability for the OCTAVE (Olympian Common Text And Vocabulary Engine) format. Basic structural competence without full architectural specifications
elevanaltd/octave-mcp 45
-
octave-mastery
Advanced semantic vocabulary and architectural patterns for the OCTAVE (Olympian Common Text And Vocabulary Engine) format. REQUIRES octave-literacy to be loaded first
elevanaltd/octave-mcp 45
-
octave-mythology
Functional mythological compression for OCTAVE (Olympian Common Text And Vocabulary Engine) documents. Semantic shorthand for LLM audiences, not prose decoration
elevanaltd/octave-mcp 45
-
octave-ultra-mythic
Ultra-high density compression using mythological atoms and semantic shorthand for OCTAVE (Olympian Common Text And Vocabulary Engine). Preserves soul and constraints at 60% compression for identity transmission, binding protocols, and extreme token scarcity.
elevanaltd/octave-mcp 45
-
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
petekp/claude-code-setup 20
-
agent-changelog
Compile an agent-optimized changelog by cross-referencing git history with plans and documentation. Use when asked to "update changelog", "compile history", "document project evolution", or proactively after major milestones, architectural changes, or when stale/deprecated information is detected that could confuse coding agents.
petekp/claude-code-setup 20
-
agent-native-architecture
Build applications where agents are first-class citizens. Use this skill when designing autonomous agents, creating MCP tools, implementing self-modifying systems, or building apps where features are outcomes achieved by agents operating in a loop.
petekp/claude-code-setup 20
-
audit-and-migrate
Slice-based, evidence-driven framework for auditing and migrating debt-heavy codebases. Use for large refactors, codebase consolidation, tech debt paydown, dependency standardization, architecture cleanup, or any multi-session migration. Also use when asked to audit the codebase, migrate from X to Y, standardize on one approach, consolidate duplicated code, or run a systematic refactor with built-in cleanup, residue sweeps, and a final ship-readiness gate. Make sure to use this skill whenever the user wants a controlled migration with slices, guardrails, handoffs, cleanup, or release closeout, even if they do not explicitly say "migration". Mentions of ratchets, slices, migration playbooks, anti-vestigial discipline, convergence, or release cleanup should strongly trigger it.
petekp/claude-code-setup 20
-
browser-use
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, or extract information from web pages.
petekp/claude-code-setup 20
-
capture-learning
Analyze recent conversation context and capture learnings to project knowledge files (for project-specific insights) or skills/commands/subagents (for cross-project patterns). Use when the user asks to "capture this learning", "update the docs with this", "remember this for next time", "document this issue", "add this to CLAUDE.md", "save this knowledge", or "update project knowledge". Also triggers after resolving build/setup issues, discovering non-obvious patterns, or completing debugging sessions with valuable insights.
petekp/claude-code-setup 20
-
every-style-editor
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.
petekp/claude-code-setup 20
-
exhaustive-systems-analysis
Perform evidence-driven, multi-subsystem audits of real codebases to find correctness bugs, race conditions, security gaps, stale documentation, dead code, and production-readiness risks. Use when asked to audit a system end-to-end, verify agent-written code before shipping, analyze a subsystem for correctness across multiple modules, or produce a structured risk report for a real implementation. Prefer other skills for a single isolated bug, a proposal or document review, or a dedicated dead-code cleanup.
petekp/claude-code-setup 20
-
explanatory-playground
Build interactive, source-linked explanatory artifacts that help someone understand a real codebase or subsystem through narrative, runtime evidence, and focused visualizations. Use when the user wants to understand how a system works, create an interactive codebase guide, build a literate walkthrough, reveal hidden state or data flow, or turn opaque code into a grounded explorable artifact. Best for request lifecycles, state machines, data pipelines, render/update behavior, event systems, algorithms, and async workflows where static code reading alone is not enough.
petekp/claude-code-setup 20
-
handoff
Generate a resume-ready handoff prompt that lets another session or agent continue work without rediscovering context. Use when the user asks for a handoff, bootstrap prompt, session summary, save-state prompt, or wants to continue later in a fresh session, another model, or a different environment. Also use when context is getting full and the current goal, repo state, decisions, verification status, blockers, and exact next actions must be preserved in a compact prompt.
petekp/claude-code-setup 20
-
improve-codebase-architecture
Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
petekp/claude-code-setup 20
-
method:dry-run
Validate a Claude Code method skill for mechanical soundness by dry-running a concrete feature through every step. Use when you need to dry run, validate a method, trace a method skill, check mechanical soundness, or verify that a method's setup, paths, commands, artifact chains, headers, templates, gates, and topology are wired correctly. Invoke this after authoring or editing any method skill, and before trusting it for real work.
petekp/claude-code-setup 20
-
method:flow-audit-and-repair
Forensic debugging workflow for broken end-to-end flows. 8 steps across 5 phases: Failure Framing → Forensics → Repair Design → Layered Repair → Reaudit. Use when an existing flow is broken, flaky, or operationally unsafe and the team needs a path from observed failure to verified repair — not for greenfield features or speculative design work.
petekp/claude-code-setup 20
-
product-design
Expert product design knowledge for software interfaces — 451 practices across 25 categories, each with tags, priority (core/situational/niche), and applies_when metadata for precise retrieval. Use this skill whenever the user is designing, reviewing, building, or discussing any part of a software interface. This includes: building forms or input flows, designing dashboards or data tables, choosing UI components (modals vs. sidebars, tabs vs. accordions, toggles vs. checkboxes), planning navigation or information architecture, handling errors and feedback, designing onboarding or empty states, building enterprise/B2B admin panels, creating design systems, implementing accessibility, optimizing perceived performance, designing search/filter/sort, building multi-step workflows or wizards, or reviewing existing designs for usability issues. Also trigger when the user asks about design best practices, UX heuristics, cognitive load, Gestalt principles, Fitts's Law, Hick's Law, or any named design principle. Even if the user doesn't explicitly say "design" — if they're building UI and making layout, component, or interaction decisions, this skill applies.
petekp/claude-code-setup 20
-
proposal-review
Facilitate methodical review of proposals (technical designs, product specs, feature requests). Use when asked to "review this proposal", "give feedback on this doc", "help me review this RFC", or when presented with a document that needs structured feedback. Handles markdown files, GitHub gists/issues/PRs, and other text formats. Chunks proposals intelligently, predicts reviewer reactions, and produces feedback adapted to the proposal's format.
petekp/claude-code-setup 20
-
swiftui-expert-skill
Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, macOS-specific APIs, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.
petekp/claude-code-setup 20