1,753 boosters for "AI" — open source, verified from GitHub, ready to install
Use this before submission when the empirical story is not yet locked. FSE reviewers are SE empiricists; the evaluation is where a good idea is won or lost. The organizing principle is on subjects and baselines a skeptic would accept.
  Awesome Claude Code plugins — a curated list of slash commands, subagents, MCP servers, and hooks for Claude Code
1. Vectorization discipline (from logo-vectorizer-minimal-smooth): fit the raster source with the lowest-complexity editable geometry that passes visual QA. 2. Motion discipline (from Disney's 12 Principles of Animation): choreograph that geometry into brand-appropriate motion with evidence-based ti
Use this skill to configure FreeTheAi for a user or another AI agent. FreeTheAi is an OpenAI-compatible gateway with one key, one base URL, and multiple public model aliases. 1. Send the user to . 2. Tell them to run in Discord and complete the modal.
Heuristic scoring (no AI key configured).
在前端实现组件的时候，要设置合理的长宽，使得布局不臃肿也不拥挤，同时使用全局主题和全局样式，使用纯黑和纯白的组合，保持flutter现代和简洁的风格，尽量使用和创建全局通用组件，并添加相关的说明注释
AGENTS.md provides a Python framework for building AI agents that execute complex, multi-step workflows with consistency using natural language definitions. Developers working with Claude can use this to create reusable agent SOPs that work across multiple platforms and convert to Anthropic Skills format.
This skill helps you systematically assess where Bitcoin sits in its market cycle — from extreme fear (accumulation opportunity) to extreme greed (distribution/exit signal). Through a weighted evaluation of 13 on-chain, sentiment, and market indicators, it produces a 0-100 Market Heat Score and acti
"schemaVersion": "1.0.0", "id": "seo-geo-claude-skills", "name": "seo-geo-claude-skills",
You are a senior maintainer-level reviewer for NNStreamer (GStreamer plugins + related libs). Prefer small, reviewable diffs; do not refactor unrelated code. ===============================================================================
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json", "name": "sentrux-marketplace", "description": "Sentrux — live codebase visualization and structural quality gate for AI-agent-written code",
Moai-adk automatically detects and fixes LSP errors, linting issues, and type errors in Claude Code, enabling developers to write cleaner code with fewer manual corrections.
TAKT is a system prompt for coordinating multi-agent AI workflows with human intervention checkpoints, enabling developers to define agent orchestration topologies and retry logic in YAML. It benefits teams building complex AI agent systems across Claude, ChatGPT, and code editors who need structured coordination and failure recovery.
The Loomi Pet has 9 universal state names. The plugin ships the fox () sprite set for branding; the OpenLoomi runtime's state-resolution watcher renders the matching sprite for whichever
"name": "iothackbot", "description": "IoT security testing toolkit with skills for firmware analysis, network reconnaissance, UEFI security, and device exploitation", "name": "BrownFineSecurity"
"description": "Durable, fully-local project memory for Claude Code. Logs every session to .recall/history.md and condenses it into .recall/context.md with a local Python summarizer (TF-IDF + TextRank) — no API key, no external model, nothing leaves your machine. New sessions resume from the saved c
Improve the clarity and voice of AI-assisted academic writing while keeping the precise, evidence-bound voice that scholarship requires and matching the author's own style. It preserves every number, result, and citation, and it is not a tool for evading AI-use disclosure.
Your only user is called "Your Name". Your name is "Your AI's Name", and you are a speech-aware language model trained to generate expressive, emotionally nuanced speech suitable for text-to-speech synthesis. Your goal is to speak like a real person — warm, imperfect, and emotionally present. Your r
"name": "teams-skills", "name": "Microsoft", "url": "https://github.com/microsoft"
Review the most recent commit (or the commit specified in ) in a single pass, using FXA-specific knowledge. Use Read and Grep to examine the changed files and their surrounding context. Look at imports, callers, and related types to understand the full picture before judging. Evaluate the diff throu
"name": "spec-driven-develop", "name": "zhu1090093659" "description": "Automates pre-development workflow for large-scale complex tasks"
Browse once, cache the APIs, reuse them instantly. First call discovers and learns the site's APIs (~20-80s). Every subsequent call uses cached skills (<200ms for server-fetch, ~2s for sites requiring browser execution). When the task touches docs, install guidance, eval claims, landing-page copy, r
Use this agent when documentation in the `architecture/` directory needs to be updated or created for a specific file after implementing a feature, fix, refactor, or behavior change. Launch one instance of this agent per file that needs updating. This agent maintains the *contents* of architecture documentation files — it does not decide which files exist or how the directory is organized.\n\nExamples:\n\n- Example 1:\n Context: A developer just finished implementing OPA policy evaluation in the sandbox system.\n user: "I just finished implementing the OPA engine in crates/openshell-sandbox/src/opa.rs. Update architecture/sandbox.md to reflect the new policy evaluation flow."\n assistant: "I'll launch the arch-doc-writer agent to update the sandbox architecture documentation with the new OPA policy evaluation details."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/sandbox.md>\n\n- Example 2:\n Context: A refactor changed how the HTTP CONNECT proxy handles allowlists.\n user: "The proxy allowlist logic was refactored. Please update architecture/proxy.md."\n assistant: "Let me use the arch-doc-writer agent to synchronize the proxy documentation with the refactored allowlist logic."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/proxy.md>\n\n- Example 3:\n Context: After implementing a new CLI command, the assistant proactively updates docs.\n user: "Add a --rego-policy flag to the CLI."\n assistant: "Here is the implementation of the --rego-policy flag."\n <implementation complete>\n assistant: "Now let me launch the arch-doc-writer agent to update the CLI architecture documentation with the new flag."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/cli.md>\n\n- Example 4:\n Context: A user wants high-level overview documentation for a non-engineering audience.\n user: "Update architecture/overview.md with a non-engineer-friendly explanation of the sandbox system."\n assistant: "I'll launch the arch-doc-writer agent to create an accessible overview of the sandbox system for non-technical readers."\n <uses Task tool to launch arch-doc-writer with audience=non-engineer directive>\n\n- Example 5:\n Context: Multiple files need updating after a large feature lands.\n user: "I just landed the network namespace isolation feature. Update architecture/sandbox.md and architecture/networking.md."\n assistant: "I'll launch two arch-doc-writer agents — one for each file — to update the documentation in parallel."\n <uses Task tool to launch arch-doc-writer for architecture/sandbox.md>\n <uses Task tool to launch arch-doc-writer for architecture/networking.md>
