auto-trigger
Workflow hook metadata for agent-playbook skills. This skill documents trigger intent between skills - DO NOT use directly, and do not assume hooks execute unless the host runtime explicitly supports them.
- Installs
- 698
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/zhaono1/agent-playbook --skill auto-trigger- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads auto-trigger automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Auto-Trigger Hooks
This skill defines trigger intent between skills. When a skill completes its workflow, a host runtime or agent may read this metadata, record a pending follow-up, and execute the next skill only when that action is supported and safe for the current session.
Hook Definitions
PRD Creation Chain
prd_complete:
triggers:
- skill: self-improving-agent
mode: background
condition: PRD file exists and is complete
- skill: session-logger
mode: auto
context: "PRD created for {feature_name}"
prd_implemented:
triggers:
- skill: session-logger
mode: auto
context: "Implemented PRD: {feature_name}"
Implementation Chain
implementation_complete:
triggers:
- skill: code-reviewer
mode: ask_first
message: "Implementation complete. Run code review?"
- skill: create-pr
mode: ask_first
condition: user_requested_submission
Session Management
session_start:
auto_triggers:
- skill: session-logger
action: create_session_file
session_end:
auto_triggers:
- skill: session-logger
action: update_session_file
Hook Format in Skills
To add auto-trigger capability to a skill, add to its front matter:
---
name: my-skill
description: Skill description
allowed-tools: Read, Write, Edit
hooks:
before_start:
- trigger: session-logger
mode: auto
context: "Start {skill_name}"
after_complete:
- trigger: self-improving-agent
mode: background
- trigger: session-logger
mode: auto
on_error:
- trigger: self-improving-agent
mode: background
---
Implementation Guide
When a skill completes its workflow:
- Check
hooksin its own front matter (before_start,after_complete,on_error,on_progress) - For each hook:
- If
mode: auto, record or run a low-risk follow-up only when the host runtime supports it - If
mode: background, record a non-blocking follow-up; do not mutate durable files silently - If
mode: ask_first, ask user before triggering - If
condition:exists, check it first
- If
- Pass context to the triggered skill
Example Integration
prd-planner should add
---
name: prd-planner
description: Creates PRDs using persistent file-based planning...
allowed-tools: Read, Write, Edit, Bash, Grep, Glob, AskUserQuestion, WebSearch
hooks:
after_complete:
- trigger: self-improving-agent
mode: background
context: "PRD created at {prd_file}"
- trigger: session-logger
mode: auto
context: "PRD creation complete"
---
self-improving-agent uses explicit validation and application gates
---
name: self-improving-agent
description: Captures redacted candidates, validates them with evidence, and records only explicitly applied rules...
allowed-tools: Read, Write, Edit, Bash, Grep, Glob
---
Its Claude failure hook is installed by the CLI adapter, not declared as
portable skill metadata. The hooks examples in this skill are declarative
intent only unless a host adapter explicitly implements them. Other hosts
should use documented adapters or manual capture.
create-pr should add
---
name: create-pr
description: Creates pull requests with bilingual documentation updates...
allowed-tools: Read, Write, Edit, Bash, Grep, AskUserQuestion
hooks:
after_complete:
- trigger: session-logger
mode: auto
context: "PR created: {pr_title}"
---
Chain Visualization
┌──────────────┐
│ prd-planner │
└──────┬───────┘
│ after_complete
├──→ self-improving-agent (background)
│ └──→ create-pr (ask_first)
│ └──→ session-logger (auto)
└──→ session-logger (auto)
Error Correction Chain
on_error:
triggers:
- skill: self-improving-agent
mode: background
context: "Error occurred in {skill_name}"
- skill: session-logger
mode: auto
context: "Error captured for {skill_name}"
Important Rules
- Don't create infinite loops - Ensure chains terminate
- Ask before major actions - Use
mode: ask_firstfor PRs, deployments, and durable file changes - Background tasks - Use
mode: backgroundfor non-blocking analysis or proposal artifacts - Pass context - Always include relevant context to triggered skills
FAQ
What does the auto-trigger skill do?
Workflow hook metadata for agent-playbook skills. This skill documents trigger intent between skills - DO NOT use directly, and do not assume hooks execute unless the host runtime explicitly supports them.
How do I install auto-trigger?
Run npx skills add https://github.com/zhaono1/agent-playbook --skill auto-trigger in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/auto-trigger/ (personal) or .claude/skills/auto-trigger/ (project).
Which AI agents can use auto-trigger?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is auto-trigger safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains auto-trigger?
It is published by zhaono1 in zhaono1/agent-playbook. It has 698 recorded installs.
More from zhaono1/agent-playbook
self-improving-agent
zhaono1/agent-playbook
Use after a failure, user correction, repeated workflow problem, or validated success reveals a reusable lesson. Captures bounded redacted candidates, runs executable behavior evals, and separates validation from application in durable guidance.
planning-with-files
zhaono1/agent-playbook
Uses persistent markdown files for general planning, progress tracking, and knowledge storage (Manus-style workflow). Use for multi-step tasks, research projects, or general organization WITHOUT mentioning PRD. For PRD-specific work, use prd-planner skill instead.
security-auditor
zhaono1/agent-playbook
Security vulnerability expert covering OWASP Top 10 and common security issues. Use when conducting security audits or reviewing code for vulnerabilities.
architecting-solutions
zhaono1/agent-playbook
Designs technical solutions and architecture. Use when user says "design solution", "architecture design", "technical design", or "方案设计" WITHOUT mentioning PRD. For PRD-specific work, use prd-planner skill instead.
skill-router
zhaono1/agent-playbook
Routes an agent request to the narrowest matching portable skill when the user asks which skill to use or needs help selecting one across supported hosts.
workflow-orchestrator
zhaono1/agent-playbook
Coordinates multi-skill workflows and records or runs follow-up actions when the host runtime supports them. Use when completing PRD creation, implementation, or any milestone that should be evaluated for additional skills.
Popular productivity & automation skills
agent-browser
vercel-labs/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. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档（Docx / Wiki）内容操作：读取、创建、编辑文档，插入或下载图片附件，以及操作思维笔记。用户提供文档 URL/token（包括 doubao.com 的 /docx/、/wiki/）时使用；按 URL 路径/token 而非域名路由；/page/ 是妙搭应用，非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive；随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格（Base）操作：建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式（BaseApp/AppMode 页面与组件）、Workspace 目录、workflow、角色权限、模板中心（多维表格模板分类/列表/搜索）；遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps；文件导入/导出转 lark-drive，认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用；doubao.com 云空间 URL/token 也按资源路径和 token 路由，不回退 WebFetch。不负责：文档内容编辑（走 lark-doc）、表格/Base 表内数据操作（走 lark-sheets/lark-base）、知识空间节点/成员管理（走 lark-wiki）、原生 Markdown 文件读写/patch/diff（走 lark-markdown）。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯：收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片（Interactive Card）、监听卡片按钮回调（card.action.trigger）。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶（添加/移除/查询置顶会话）、管理标签数据、处理卡片回调时使用。