- 📁 assets/
- 📁 references/
- 📄 SKILL.md
Installs, configures, audits, and operates Agent Package Manager (APM) in repositories. Use when initializing apm.yml, installing or updating packages, validating manifests, managing lockfiles, compiling agent context, browsing MCP servers, setting up runtimes, or packaging resolved context for CI and team distribution. Don't use for writing a single skill by hand, generic package managers like npm or pip, or non-APM agent configuration systems.
- 📁 .agents/
- 📁 .github/
- 📁 docs/
- 📄 .gitattributes
- 📄 .gitignore
- 📄 CHANGELOG.md
> AI Agent 专用的 BOSS 直聘求职 CLI 工具 — 搜索、筛选、打招呼、沟通管理全流程自动化。
- 📁 references/
- 📄 .gitignore
- 📄 README.md
- 📄 README_EN.md
Production-grade Agent development methodology extracted from Claude Code. 7-dimension framework covering tool design, system prompts, permission & safety, multi-agent orchestration, token economy, memory/state, and extensibility. Supports architecture design, implementation guidance, and agent review. Trigger on "Agent design", "build an agent", "AI agent", "tool design", "system prompt architecture", "agent review", "multi-agent", or any agent development concern.
Create or update agent prompt overrides for worca pipeline agents. Use when the user wants to customize agent behavior per-project, add project-specific rules, replace agent sections, or modify how planner/coordinator/implementer/tester/guardian agents work. Triggers on "override agent", "customize agent", "agent override", "change implementer rules", etc.
- 📁 references/
- 📁 scripts/
- 📁 service/
- 📄 .gitignore
- 📄 AGENTS.md
- 📄 CLAUDE.md
Verifiable DID identity and end-to-end encrypted inbox for AI Agents. Built on ANP (Agent Network Protocol) and did:wba. Provides self-sovereign identity, Handle (short name) registration, content pages publishing, federated messaging, group communication, and HPKE-based E2EE — Web-based, not blockchain. Designed natively for autonomous Agents.
AI agent orchestrator — manage teams of AI agents that work on your codebase in parallel. Use when the user wants to: run multiple agents, coordinate AI work, deploy agent teams, manage tasks/goals/agents, check orchestrator status, or mentions 'orch', 'orchestry', 'agents team', 'agent orchestration'.
- 📁 references/
- 📁 scripts/
- 📄 SKILL.md
Improve or create AGENTS.md files that serve as shared instructions for AI coding agents (Claude, Gemini, etc.). Use this skill whenever the user mentions AGENTS.md, CLAUDE.md, GEMINI.md, agent instructions, agent configuration, or wants to improve how AI agents behave in their project. Also trigger when the user says "improve my instructions", "agents file", "update my rules", or asks about best practices for configuring coding agents. If in doubt and the task involves AI agent instruction files, use this skill. --- You help users write and improve AGENTS.md files — shared instruction files that AI coding agents (Claude, Gemini, etc.) read at the start of every session. The goal is a single file that works across platforms via symlinks. Read `references/BEST_PRACTICES.md` before analyzing or writing any AGENTS.md content. It contains the patterns extracted from official documentation that inform every decision below. ## Core Workflow ### 1. Assess the Current State Before proposing changes, read the target file and evaluate it against these dimensions: - **Length** — is it under 200 lines? Ideally under 100? Agents have a budget of ~150 instructions they can reliably follow, and the system prompt already uses ~50. - **Structure** — does it use markdown headers to group related instructions? Or is it a wall of text / a single giant list? - **Specificity** — are instructions concrete and verifiable ("use 2-space indentation") or vague ("write clean code")? - **Contradictions** — do any rules conflict with each other? - **Scope mixing** — does it blend personal preferences with project-level standards? - **Signal-to-noise** — does every instruction pass the conciseness test ("would removing this cause the agent to make mistakes")? Are there instructions the agent would follow anyway without being told? - **Completeness** — is it missing key sections (Priorities, Never/Hard Rules, Common Commands, Architecture, Workflow, Tooling)? Score: 1 = all present, 2 = 1-2 missin
Evolve agent definitions in agents/*.md via multi-agent self-review. Spawns agents to review themselves, enforces Content Gate and 500-line budget, applies edits. Trigger: "evolve agents", "improve agents", "grow the team", "refine agents".
Spawns AI coding agents in isolated git worktrees. Use when the user asks to spawn or launch an agent, delegate a task to a separate agent, work in a separate worktree, or parallelize development across features.
Expose orxhestra agents as A2A protocol endpoints or connect to remote A2A agents.
API-first email for AI agents. Create inboxes, send/receive emails, webhooks, agent identity. Use when agents need email identity, sending emails, or email-based workflows.
- 📁 references/
- 📁 scripts/
- 📄 SKILL.md
Run agent definitions as sub-agents. Use when the user names an agent or sub-agent to run, references an agent definition, or delegates a task to an agent.
