Go Micro is a framework for distributed systems development in Go. It provides pluggable abstractions for service discovery, RPC, pub/sub, config, auth, storage, and more. The framework is evolving into an AI-native platform where every microservice is automatically accessible to AI agents via the Model Context Protocol (MCP).
Note: This file is committed to a public OSS repository. Never add sensitive information (API keys, internal URLs, credentials, private infrastructure details) here. n8n-mcp is an MCP (Model Context Protocol) server that gives AI assistants access to n8n node documentation, workflow validation, and workflow management. Documentation and validation tools work offline against a bundled SQLite database of node information; management tools (n8n_*) operate on a live n8n instance when API credentials are configured. Key subsystems of src/ (non-exhaustive — smaller…
Follow these steps to refresh Claude Code's local environment, ensuring that their agent skills and plugins are fully up-to-date. Use Claude Code's native plugin manager instead of npx. 1. Update the Plugin: Run the specific CLI command to update the Firebase plugin:
Follow AGENTS.md for the development workflow and CONTRIBUTING.md for the contribution policy. Pull requests from everyone are welcome for direct review and merging, regardless of contributor or maintainer status. Preserve unrelated work and obtain user authorization before merging.
Guidance for Claude Code working in this repository. Follow conventions in CONTRIBUTING.md. notebooklm-py is an unofficial async Python client for Google NotebookLM, driving Google's internal batchexecute RPC protocol to automate notebooks, sources, chat, and studio artifacts. Critical constraint: Obfuscated RPC method IDs in src/notebooklm/rpc/_identifiers.py are undocumented and Google changes them periodically — the #1 breakage class. rpc/types.py re-exports them for backwards compatibility. See docs/installation.md for the full installation guide. Always install the full extras set (mcp, server, impersonate); omitting them…
Paseo is a mobile app for monitoring and controlling your local AI coding agents from anywhere. Your dev environment, in your pocket. Connects directly to your actual development environment —…
This is the main repo of Parlant (https://parlant.io). Parlant is a Python based agent framework. Its core strengths: The repo's structure follows the Hexagonal Architecture (Ports and Adapters) approach. General Coding Instructions: Always follow this plan when asked to code a feature or fix a bug: 1. Consider the codebase's structure 2. Describe your implementation plan, including: a. What tests you will write (test names + files they would live in) b. Why do you think the tests would initially…
Agent Skills for Context Engineering is an open collection of Agent Skills teaching context engineering and harness engineering principles for production AI agent systems. Skills are platform-agnostic (Claude Code, Cursor, Codex/OpenAI Agent Skills, GitHub Copilot, any Open Plugins-conformant tool). v2.5.0 adds the long-horizon-prompting skill (pseudo-formal task briefs for long-running autonomous agents and parallel orchestrations) on top of the self-improvement-loops skill (v2.4.0) and the file-based researcher operating system with deterministic gates, cross-platform Agent Skills validation, and a continuous loop. Use the…
Wren is an open-source semantic engine for MCP clients and AI agents. It translates SQL queries through a semantic layer (MDL — Modeling Definition Language) and executes them against 22+…
Long-running Node server (Hono): browser chat with a sessions sidebar (useChat → /api/chat) → Chat SDK web adapter onDirectMessage → one Managed Agents session per conversation, where the conversation ID is the session ID (no mapping, no database; the sidebar is sessions.list, transcript replay is sessions.events.list) → a held session event stream (opened with event_deltas token previews, always on) feeds each fragment back onto the same HTTP response while /api/activity streams the tool calls and thinking the page shows as…
This directory is a Managed Agents cookbook: it builds a real M&A data room into a knowledge wiki (a versioned memory store) and queries it. The runnable artifact is distilldocumentsintoknowledgewiki.ipynb; everything else exists to set that notebook up. When a user asks you to walk them through setting this quickstart up, read skill.md in this directory and follow it step by step. Do not improvise the setup — the SDK build, the SEC user-agent, and the fetch order all matter.
MCP server that exposes Managed Agents session primitives as tools. Two entrypoints sharing one tool set: src/server.ts (stdio → Claude Desktop and Claude Code) and src/server-http.ts (Streamable HTTP → claude.ai custom connector). This quickstart creates no agents, so there is no agents/ directory. It needs one environment, created once from environment.yaml (the command is in that file and in README.md). Commands: bun run stdio (Desktop, Code), bun run http (claude.ai), bun run typecheck.
A Next.js chat built directly on a Managed Agent session: no chat framework, the event log is the app state. Teaches session event streaming (eventdeltas), vault credential injectionlocation, per-session agentwithoverrides, and multiagent coordinator rosters. The planner calls the National Park Service and Windy APIs with keys it never holds, then hands its draft to a second agent for a quick critique. That second agent is an Opus reviewer running as a session thread. 1. Invoke /claude-api first. It loads the…
Scheduled deployment: cron → Managed Agents session with sentry-cli and a vault env-var credential → triage report in /mnt/session/outputs/. Pull exact shapes from the /claude-api skill's shared/managed-agents-*.md docs. Provisioning is ./agents/setup.sh (ant 1.34 or later, jq): it runs ant apply --yes agents environments vaults, which creates the agent, environment, and vault from those directories and records their IDs in claude-lock.json, then adds the Sentry token to the vault as an environmentvariable credential (skipped when the vault already has one), and…
For requests to add A2UI rendering to AG-UI applications or to scaffold an AG-UI + A2UI quickstart, use skills/ag-ui-a2ui-integration/SKILL.md. AG-UI is an event-based protocol that standardizes agent-user interactions. The codebase is organized as a monorepo with the following structure:
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.