跳到主内容
智客 ZICQ

技能库 智客分类:文档办公 github-actions-docs

Github Actions Docs

当用户询问如何写出,解释,自定义,迁移,安全,或故障排除 GitHub 动作工作流程,工作流程语法,触发,矩阵,跑取,可重复使用的工作流程,文物,缓存,秘密,OIDC,部署,自定义动作,或动作跑取控制器,特别是当他们需要正式的 GitHub 文档,精确链接,或docs-基于的YAML 引导时.

13 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

当用户询问如何写出,解释,自定义,迁移,安全,或故障排除 GitHub 动作工作流程,工作流程语法,触发,矩阵,跑取,可重复使用的工作流程,文物,缓存,秘密,OIDC,部署,自定义动作,或动作跑取控制器,特别是当他们需要正式的 GitHub 文档,精确链接,或docs-基于的YAML 引导时.

何时用

当请求涉及:

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:When to Use、Workflow、1. Classify the request、2. Search official GitHub docs first、3. Open the best page before answering、4. Answer with docs-grounded guidance。 其中含规范建议的小节:分步指令。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/topic-map.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Use when users ask how to write, explain, customize, migrate, secure, or troubleshoot GitHub Actions workflows, workflow syntax, triggers, matrices, runners, reusable workflows, artifacts, caching, secrets, OIDC, deployments, custom actions, or Actions Runner Controller, especially when they need official GitHub documentation, exact links, or docs-grounded YAML guidance.

When to UseWorkflow1. Classify the request2. Search official GitHub docs first3. Open the best page before answering4. Answer with docs-grounded guidanceAnswer ShapeSearch and Routing TipsCommon MistakesBundled Reference

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
github-actions-docs
description
Use when users ask how to write, explain, customize, migrate, secure, or troubleshoot GitHub Actions workflows, workflow syntax, triggers, matrices, runners, reusable workflows, artifacts, caching, secrets, OIDC, deployments, custom actions, or Actions Runner Controller, especially when they need official GitHub documentation, exact links, or docs-grounded YAML guidance.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 1
  • references/topic-map.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「github-actions-docs」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-b8a0f91ef57c3144-Github-%E5%8A%A8%E4%BD%9C%E6%96%87%E4%BB%B6.html
请存为 .cursor/skills/github-actions-docs/SKILL.md 或 .claude/skills/github-actions-docs/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/xixu-me/skills 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/xixu-me/skills' --list

npx skills add 'https://github.com/xixu-me/skills' --skill 'github-actions-docs'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: github-actions-docs description: Use when users ask how to write, explain, customize, migrate, secure, or troubleshoot GitHub Actions workflows, workflow syntax, triggers, matrices, runners, reusable workflows, artifacts, caching, secrets, OIDC, deployments, custom actions, or Actions Runner Controller, especially when they need official GitHub documentation, exact links, or docs-grounded YAML guidance. --- GitHub Actions questions are easy to answer from stale memory. Use this skill to ground answers in official GitHub documentation and return the closest authoritative page instead of generic CI/CD advice. ## When to Use Use this skill when the request is about: - GitHub Actions concepts, terminology, or product boundaries - Workflow YAML, triggers, jobs, matrices, concurrency, variables, contexts, or expressions - GitHub-hosted runners, larger runners, self-hosted runners, or Actions Runner Controller - Artifacts, caches, reusable workflows, workflow templates, or custom actions - Secrets, `GITHUB_TOKEN`, OpenID Connect, artifact attestations, or secure workflow patterns - Environments, deployment protection rules, deployment history, or deployment examples - Migrating from Jenkins, CircleCI, GitLab CI/CD, Travis CI, Azure Pipelines, or other CI systems - Troubleshooting workflow behavior when the user needs documentation, syntax guidance, or official references Do not use this skill for: - A specific failing PR check, missing workflow log, or CI failure triage. Use `gh-fix-ci`. - General GitHub pull request, branch, or repository operations. Use `github`. - CodeQL-specific configuration or code scanning guidance. Use `codeql`. - Dependabot configuration, grouping, or dependency update strategy. Use `dependabot`. ## Workflow ### 1. Classify the request Decide which bucket the question belongs to before searching: - Getting started or tutorials - Workflow authoring and syntax - Runners and execution environment - Security and supply chain - Deployments and environments - Custom actions and publishing - Monitoring, logs, and troubleshooting - Migration If you need a quick starting point, load `references/topic-map.md` and jump to the closest section. ### 2. Search official GitHub docs first - Treat `docs.github.com` as the source of truth. - Prefer pages under . - Search with the user's exact terms plus a focused Actions phrase such as `workflow syntax`, `OIDC`, `reusable workflows`, or `self-hosted runners`. - When multiple pages are plausible, compare 2-3 candidate pages and pick the one that most directly answers the user's question. ### 3. Open the best page before answering - Read the most relevant page, and the exact section when practical. - Use the topic map only to narrow the search space or surface likely starting pages. - If a page appears renamed, moved, or incomplete, say that explicitly and return the nearest authoritative pages instead of guessing. ### 4. Answer with docs-grounded guidance - Start with a direct answer in plain language. - Include exact GitHub docs links, not just the docs homepage. - Only provide YAML or step-by-step examples when the user asks for them or when the docs page makes an example necessary. - Make any inference explicit. Good phrasing: - `According to GitHub docs, ...` - `Inference: this likely means ...` ## Answer Shape Use a compact structure unless the user asks for depth: 1. Direct answer 2. Relevant docs 3. Example YAML or steps, only if needed 4. Explicit inference callout, only if you had to connect multiple docs pages Keep citations close to the claim they support. ## Search and Routing Tips - For concept questions, prefer overview or concept pages before deep reference pages. - For syntax questions, prefer workflow syntax, events, contexts, variables, or expressions reference pages. - For security questions, prefer `Secure use`, `Secrets`, `GITHUB_TOKEN`, `OpenID Connect`, and artifact attestation docs. - For deployment questions, prefer environments and deployment protection docs before cloud-specific examples. - For migration questions, prefer the migration hub page first, then a platform-specific migration guide. - If the user asks for a beginner walkthrough, start with a tutorial or quickstart instead of a raw reference page. ## Common Mistakes - Answering from memory without verifying the current docs - Linking the GitHub Actions docs landing page when a narrower page exists - Mixing up reusable workflows and composite actions - Suggesting long-lived cloud credentials when OIDC is the better documented path - Treating repo-specific CI debugging as a documentation question when it should be handed to `gh-fix-ci` - Letting adjacent domains absorb the request when `codeql` or `dependabot` is the sharper fit ## Bundled Reference Read `references/topic-map.md` only as a compact index of likely doc entry points. It is intentionally incomplete and should never replace the live GitHub docs as the final authority.

相关技能

文档办公

Ontology

为结构化的代理内存和可堆肥技能所打入的知识图. 在创建/征服实体(Person, project, Task, Evention, Document)时使用,链接相关对象,强制约束,规划多步动作作为图变,或技能需要共享状态时使用. 触发到"记住","我知道什么","链接X到Y",…

文档办公

Nano Pdf

使用纳米-pdf CLI编辑带有自然语言指令的PDF.

文档办公

Word / DOCX

创建,检查,并编辑有可靠样式的Microsoft Word文档和DOCX文件,编号,跟踪更改,表格,章节,并进行相容性检查. 当 (1) 任务涉及 Word 或 ".docx " 时使用; (2) 文件包括跟踪的更改,评论,字段,表格,模板,或页面布局限制; (3) 文档必须在不…

文档办公

Api Gateway

通过 Maton 网关调用第三方 API, 它为用户已经连接的应用程序注入证书 。 当用户命名一个连接的应用程序和其中的具体行动时使用此技能——读取一个邮箱,查询一个CMM,归档一个问题,更新一个电子表格,通过一个连接的搜索或刮取提供者运行一个查询. 每一次通话都到用户连接的应用…