By sickn33
Automate editorial workflows across Airtable, Google Sheets, Notion, Slack, and Make, plus web scraping with Playwright/Puppeteer and MCP server creation for durable workflow orchestration.
Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views. Always search tools first for current schemas.
Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, and anti-detection patterns.
Automate Google Sheets operations (read, write, format, filter, manage spreadsheets) via Rube MCP (Composio). Read/write data, manage tabs, apply formatting, and search rows programmatically.
Automate Make (Integromat) tasks via Rube MCP (Composio): operations, enums, language and timezone lookups. Always search tools first for current schemas.
Create MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. The quality of an MCP server is measured by how well it enables LLMs to accomplish real-world tasks.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A complete local skill catalog for coding agents—from project inspection and agent-owned selection to a reproducible, reviewable plan.
Current release: V15.1.0. This release includes AAS Core for complete local catalog search, agent-owned selection, manifest validation, planning, and diagnosis. Apply and recovery remain experimental and outside the supported preview path.
Codex or Claude inspects your project, enumerates its primary capabilities, searches and compares candidates across the complete local AAS catalog, and chooses the exact skills. Core imposes no semantic policy that favors a small stack; the manifest format has an explicit technical maximum of 128 skills. All 1,968 skills in the current catalog remain individually searchable, readable, and selectable. AAS Core does not rank or recommend skills. Its read-only compose_stack tool validates and returns the agent-owned manifest in memory; a client or the aas CLI persists the reviewed stack and its optional selection-evidence sidecar.
Read the AAS Core preview guide →
Project
-> inspected by Codex or Claude (not by AAS)
-> agent searches and reads the complete local catalog
-> AAS MCP (local stdio, read-only)
-> Codex or Claude chooses exact skill IDs
-> compose_stack validates the selection in memory (read-only)
-> client or AAS CLI persists aas-stack.json and optional evidence
-> AAS CLI validate + immutable plan preview
-> human review (optionally in Workbench)
The 1,967+ reusable SKILL.md playbooks, specialized plugins, bundles, workflows, and direct installers remain important. They are the content, curation, distribution, and compatibility layers around AAS Core—not competing primary products.
This is an independent community project. It is not affiliated with, sponsored by, endorsed by, or authorized by Google. Google, Antigravity, Gemini, and related product names are referenced only to describe compatibility and install targets. The GitHub repository is canonical; the hosted catalog and browser-local Workbench are companion discovery and review surfaces, not a hosted control plane.
The agent composes. You control. AAS keeps the stack reproducible.
AAS Core gives the repository one product model:
Plugin-safe Claude Code distribution of Agentic Awesome Skills with 1,933 supported skills.
Editorial "AAS Security Engineer" bundle for Claude Code from Agentic Awesome Skills.
Plugin-safe Claude Code distribution of Agentic Awesome Skills with 1,916 supported skills.
Editorial "Web Designer" bundle for Claude Code from Agentic Awesome Skills.
Editorial "AAS QA & Test Automation" bundle for Claude Code from Agentic Awesome Skills.
npx claudepluginhub sickn33/agentic-awesome-skills --plugin agentic-bundle-automation-builderEditorial "Automation Builder" bundle for Claude Code from Antigravity Awesome Skills.
Generate n8n automation workflows from natural language descriptions
Design complex n8n workflows with AI assistance - loops, branching, error handling
Production-grade n8n workflow building skills. Pairs with the official n8n instance-level MCP server to teach Claude how to architect, validate, and ship workflows that work in production.
Expert skills for designing, building, and deploying Make.com automation scenarios — for Claude Code and other AI agents
Use this agent when you need to design, build, or validate n8n automation workflows. This agent specializes in creating efficient n8n workflows using proper validation techniques and MCP tools integration.\n\nExamples:\n- <example>\n Context: User wants to create a Slack notification workflow when a new GitHub issue is created.\n user: "I need to create an n8n workflow that sends a Slack message whenever a new GitHub issue is opened"\n assistant: "I'll use the n8n-workflow-builder agent to design and build this GitHub-to-Slack automation workflow with proper validation."\n <commentary>\n The user needs n8n workflow creation, so use the n8n-workflow-builder agent to handle the complete workflow design, validation, and deployment process.\n </commentary>\n</example>\n- <example>\n Context: User has an existing n8n workflow that needs debugging and optimization.\n user: "My n8n workflow keeps failing at the HTTP Request node, can you help me fix it?"\n assistant: "I'll use the n8n-workflow-builder agent to analyze and debug your workflow, focusing on the HTTP Request node configuration."\n <commentary>\n Since this involves n8n workflow troubleshooting and validation, use the n8n-workflow-builder agent to diagnose and fix the issue.\n </commentary>\n</example>\n- <example>\n Context: User wants to understand n8n best practices and available nodes for a specific use case.\n user: "What are the best n8n nodes for processing CSV data and sending email reports?"\n assistant: "I'll use the n8n-workflow-builder agent to explore the available nodes and recommend the best approach for CSV processing and email automation."\n <commentary>\n This requires n8n expertise and node discovery, so use the n8n-workflow-builder agent to provide comprehensive guidance.\n </commentary>\n</example>