[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DEPWTH5C4MJRVRMANSTEZE":3,"skill-same:01M7DEPWTH5C4MJRVRMANSTEZE":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7DEPWTH5C4MJRVRMANSTEZE","actions-workflows",null,"Use when writing, reviewing, or debugging GitHub Actions or Gitea Actions workflows — covers security hardening, concurrency, job structure, permissions, engine differences, and mirror patterns","kejadlen\u002Fdotfiles","kejadlen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F8639?v=4","01M7DEPV4SN2WBW50SBF2KG7D1","Alpha Chen","01M7DEPV5FBX0YWCBKEVHKT8E2",10,"MIT","https:\u002F\u002Fgithub.com\u002Fkejadlen\u002Fdotfiles\u002Fblob\u002Fmain\u002Fai\u002Fskills\u002Factions-workflows\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: actions-workflows\ndescription: Use when writing, reviewing, or debugging GitHub Actions or Gitea Actions workflows — covers security hardening, concurrency, job structure, permissions, engine differences, and mirror patterns\n---\n\n# Actions workflows\n\n*This is a self-improving skill. If you used it and it came up short — a missing command, flag, gotcha, or workflow — invoke the `self-improving-skills` skill and follow it before you finish.*\n\nGitea Actions is a GitHub Actions-compatible engine. Same YAML, same\n`${{ github.* }}` contexts, same `$GITHUB_OUTPUT`\u002F`$GITHUB_ENV`\nconventions, same public action marketplace. Workflows live in\n`.github\u002Fworkflows\u002F` or `.gitea\u002Fworkflows\u002F`; every pattern in this\nskill works in both unless a section says otherwise.\n\nGitea's self-hosted runners are minimal — don't assume `rustup`,\n`gh`, `just`, or similar tools are preinstalled. Install what you need\ninline or build a custom runner image.\n\n## The mirror pattern\n\nSelf-host the canonical repo on Gitea, mirror to GitHub to offload\nreleases. The goal is to keep the code on infrastructure you control\nwhile still getting the GitHub ecosystem for anything release-facing:\nhosted cross-platform runners, dotslash publishing, GHCR, and the\ndownload reach that comes with GitHub Releases. The mirror is\nread-only — nobody commits to it.\n\nThe split:\n\n- Gitea runs day-to-day CI (tests, lint, coverage) and the tagging\n  workflow. This is where you push.\n- GitHub runs on `push: tags: [v*]` to build release artifacts and\n  publish them. The mirror is the only writer.\n\nRanger uses this pattern: Gitea's `release.yml` pushes a\n`v\u003Ccalver>+\u003Csha>` tag, the mirror propagates the tag to GitHub, and\nGitHub's `release.yml` picks it up and builds macOS and Linux\nbinaries. The GitHub side can use triggers that would be risky on a\nrepo accepting fork PRs, because the mirror doesn't accept them.\n\nWhen splitting, annotate the GitHub workflow's trigger so zizmor\nunderstands the context:\n\n```yaml\non: # zizmor: ignore[dangerous-triggers] -- only triggers on tag pushes from Gitea mirror; no fork PR risk.\n  push:\n    tags: [v*]\n```\n\n## Security\n\nDefault-deny permissions. Set `permissions: {}` at the workflow level,\nthen grant the minimum each job needs. Every permission line gets a\ncomment explaining why — no bare permissions:\n\n```yaml\npermissions: {}\n\njobs:\n  test:\n    permissions:\n      contents: read  # checkout.\n      packages: write # push container image to GHCR.\n```\n\nPin actions to full commit SHAs, not tags. Tags are mutable — a\ncompromised action can be re-tagged. Add a version comment for humans:\n\n```yaml\n- uses: actions\u002Fcheckout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6\n```\n\nThis applies on Gitea too, even though actions are proxied through\nthe Gitea instance. The upstream repo is still the source of truth.\n\nDisable credential persistence on checkout to prevent tokens from\nleaking to later steps:\n\n```yaml\n- uses: actions\u002Fcheckout@\u003Csha> # v6\n  with:\n    persist-credentials: false\n```\n\nThis breaks `git push` from later steps. On GitHub, use `gh release\ncreate --target \"${GITHUB_SHA}\"` to create the tag and release via the\nAPI. On Gitea, use `tea releases create` or a direct API call with a\nscoped token. If you truly need `git push` (for example, to push a\ntag), scope the credentials to the single step that needs them —\ndon't leave them persistent for the whole job.\n\n`gh release create` creates the tag too when it doesn't exist yet, so a\nbuild workflow can cut its own release in one step. It needs `contents:\nwrite` and an explicit `GH_TOKEN` — the `gh` CLI does not pick up the\njob token on its own:\n\n```yaml\n- name: Create GitHub release\n  env:\n    GH_TOKEN: ${{ github.token }}\n    VERSION: ${{ github.event.inputs.version }}\n  run: |\n    gh release create \"v$VERSION\" \\\n      --target \"$GITHUB_SHA\" \\\n      --title \"v$VERSION\" \\\n      --notes \"Released from $GITHUB_SHA.\"\n```\n\nKeep backticks out of `--notes`. An unquoted heredoc or a double-quoted\nstring runs them as command substitution, and quoting the heredoc\ndelimiter to stop that also kills the variable expansion you wanted.\nWrite the notes without code spans, or build a notes file and pass\n`--notes-file`.\n\nIndirect environment variable expansion. Never interpolate expressions\ndirectly in `run:` scripts — an attacker-controlled value (branch\nname, PR title, issue body) can inject shell commands. Assign\nexpressions to env vars first:\n\n```yaml\n# wrong — injectable.\n- run: echo \"${{ github.event.pull_request.title }}\"\n\n# correct — safe expansion.\n- env:\n    PR_TITLE: ${{ github.event.pull_request.title }}\n  run: echo \"$PR_TITLE\"\n```\n\nName the env var after the expression path, uppercased with\nunderscores: `${{ steps.meta.outputs.version }}` →\n`STEPS_META_OUTPUTS_VERSION`, `${{ needs.build.outputs.image }}` →\n`NEEDS_BUILD_OUTPUTS_IMAGE`.\n\n## Concurrency\n\nCancel in-progress PR runs. Use the workflow name and ref as the\nconcurrency key, and only cancel for PRs (not pushes to main):\n\n```yaml\nconcurrency:\n  group: ${{ github.workflow }}-${{ github.ref }}\n  cancel-in-progress: ${{ github.event_name == 'pull_request' }}\n```\n\nSerialize deploys. Use a fixed group name with `cancel-in-progress:\ntrue` so only the latest deploy runs:\n\n```yaml\nconcurrency:\n  group: fly-deploy\n  cancel-in-progress: true\n```\n\n## Job structure\n\nSeparate test, build, and deploy. Use `needs:` to express dependencies\nand `if:` to gate jobs on context:\n\n```yaml\njobs:\n  test:\n    # runs on all pushes and PRs.\n  build:\n    needs: test\n    if: github.ref == 'refs\u002Fheads\u002Fmain' && github.event_name == 'push'\n  deploy:\n    needs: build\n    if: github.ref == 'refs\u002Fheads\u002Fmain' && github.event_name == 'push'\n```\n\nPass data between jobs with outputs. Declare outputs in the producing\njob and reference them downstream. Assign the output to an env var\nrather than interpolating in `run:`:\n\n```yaml\nbuild:\n  outputs:\n    image: ghcr.io\u002F${{ github.repository }}:${{ steps.meta.outputs.version }}\n\ndeploy:\n  needs: build\n  steps:\n    - run: flyctl deploy --image \"$IMAGE\"\n      env:\n        IMAGE: ${{ needs.build.outputs.image }}\n```\n\n## Environments (GitHub only)\n\nUse GitHub environments for deploy protection rules and\nenvironment-scoped secrets. For PR previews, key the name on the PR\nnumber:\n\n```yaml\npreview:\n  environment:\n    name: pr-${{ github.event.number }}\n    url: ${{ steps.deploy.outputs.url }}\n```\n\nGitea doesn't have a fully equivalent environments feature. For Gitea,\nuse repo-level or org-level secrets and gate sensitive jobs with `if:`\nconditions instead.\n\n## Zizmor\n\nStatic analysis for Actions workflows. Catches template injection,\nexcessive permissions, unpinned actions, credential leaks, and more.\nRun `zizmor --help` for full options. Zizmor treats Gitea and GitHub\nworkflows the same way — point it at both directories.\n\nAlways add a zizmor audit job to CI. For a repo with both directories,\npass them explicitly:\n\n```yaml\nzizmor:\n  runs-on: ubuntu-latest\n  permissions:\n    contents: read         # checkout.\n    security-events: write # upload SARIF to code scanning (GitHub only — drop on Gitea).\n  steps:\n    - uses: actions\u002Fcheckout@\u003Csha> # v6\n      with:\n        persist-credentials: false\n    - uses: zizmorcore\u002Fzizmor-action@\u003Csha>\n      with:\n        inputs: .gitea\u002Fworkflows\u002F* .github  # audit both sets.\n        advanced-security: false             # set true on GitHub for SARIF upload.\n        annotations: true\n```\n\nOn Gitea, drop `security-events: write` and the SARIF upload — leave\n`annotations: true` so findings show up in the run log.\n\nLocal usage. `zizmor .` only discovers `.github\u002Fworkflows\u002F` — pass\n`.gitea\u002Fworkflows\u002F*` explicitly on a dual-engine repo, or it silently\nskips every Gitea workflow:\n\n```bash\nzizmor .gitea\u002Fworkflows\u002F* .github   # audit both directories.\nzizmor .gitea\u002Fworkflows\u002Fci.yml      # single file.\nzizmor --fix .gitea\u002Fworkflows\u002F* .github\nzizmor --pedantic .gitea\u002Fworkflows\u002F* .github\n```\n\nConfigure with `zizmor.yml` in the repo root, `.github\u002F`, or\n`.gitea\u002F`. Ignore inline with a justification after `--`:\n\n```yaml\non:\n  workflow_run: # zizmor: ignore[dangerous-triggers] -- scoped to main branch, checks conclusion.\n```\n\n## Renovate integration\n\nOn GitHub, pin action SHAs and let Renovate update them. The\n`github-actions` manager detects `uses:` lines automatically — no\nextra config needed.\n\nOn Gitea, Renovate works but needs the workflow paths configured —\nits `github-actions` manager looks at `.github\u002Fworkflows\u002F` by default.\nExtend `fileMatch` in `renovate.json`:\n\n```json\n{\n  \"github-actions\": {\n    \"fileMatch\": [\"(^|\u002F)\\\\.gitea\u002Fworkflows\u002F[^\u002F]+\\\\.ya?ml$\"]\n  }\n}\n```\n\n## Quick reference\n\n| What | How |\n|---|---|\n| Set step output | `echo \"key=value\" >> \"$GITHUB_OUTPUT\"` |\n| Set env for later steps | `echo \"KEY=value\" >> \"$GITHUB_ENV\"` |\n| Conditional job | `if: github.ref == 'refs\u002Fheads\u002Fmain'` |\n| Conditional step | `if: github.event.action != 'closed'` |\n| Job dependency | `needs: [test, lint]` |\n| Job output | `outputs: { version: ${{ steps.x.outputs.version }} }` |\n| Consume job output | `${{ needs.build.outputs.version }}` |\n| Cancel previous runs | `cancel-in-progress: true` in `concurrency:` |\n| Required permissions | `permissions:` block per job |\n| GitHub CLI in a step | `env: { GH_TOKEN: ${{ github.token }} }` |\n| Gitea CLI in a step | `env: { TEA_TOKEN: ${{ secrets.TEA_TOKEN }} }` |\n","# Actions workflows\n\n*This is a self-improving skill. If you used it and it came up short — a missing command, flag, gotcha, or workflow — invoke the `self-improving-skills` skill and follow it before you finish.*\n\nGitea Actions is a GitHub Actions-compatible engine. Same YAML, same\n`${{ github.* }}` contexts, same `$GITHUB_OUTPUT`\u002F`$GITHUB_ENV`\nconventions, same public action marketplace. Workflows live in\n`.github\u002Fworkflows\u002F` or `.gitea\u002Fworkflows\u002F`; every pattern in this\nskill works in both unless a section says otherwise.\n\nGitea's self-hosted runners are minimal — don't assume `rustup`,\n`gh`, `just`, or similar tools are preinstalled. Install what you need\ninline or build a custom runner image.\n\n## The mirror pattern\n\nSelf-host the canonical repo on Gitea, mirror to GitHub to offload\nreleases. The goal is to keep the code on infrastructure you control\nwhile still getting the GitHub ecosystem for anything release-facing:\nhosted cross-platform runners, dotslash publishing, GHCR, and the\ndownload reach that comes with GitHub Releases. The mirror is\nread-only — nobody commits to it.\n\nThe split:\n\n- Gitea runs day-to-day CI (tests, lint, coverage) and the tagging\n  workflow. This is where you push.\n- GitHub runs on `push: tags: [v*]` to build release artifacts and\n  publish them. The mirror is the only writer.\n\nRanger uses this pattern: Gitea's `release.yml` pushes a\n`v\u003Ccalver>+\u003Csha>` tag, the mirror propagates the tag to GitHub, and\nGitHub's `release.yml` picks it up and builds macOS and Linux\nbinaries. The GitHub side can use triggers that would be risky on a\nrepo accepting fork PRs, because the mirror doesn't accept them.\n\nWhen splitting, annotate the GitHub workflow's trigger so zizmor\nunderstands the context:\n\n```yaml\non: # zizmor: ignore[dangerous-triggers] -- only triggers on tag pushes from Gitea mirror; no fork PR risk.\n  push:\n    tags: [v*]\n```\n\n## Security\n\nDefault-deny permissions. Set `permissions: {}` at the workflow level,\nthen grant the minimum each job needs. Every permission line gets a\ncomment explaining why — no bare permissions:\n\n```yaml\npermissions: {}\n\njobs:\n  test:\n    permissions:\n      contents: read  # checkout.\n      packages: write # push container image to GHCR.\n```\n\nPin actions to full commit SHAs, not tags. Tags are mutable — a\ncompromised action can be re-tagged. Add a version comment for humans:\n\n```yaml\n- uses: actions\u002Fcheckout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6\n```\n\nThis applies on Gitea too, even though actions are proxied through\nthe Gitea instance. The upstream repo is still the source of truth.\n\nDisable credential persistence on checkout to prevent tokens from\nleaking to later steps:\n\n```yaml\n- uses: actions\u002Fcheckout@\u003Csha> # v6\n  with:\n    persist-credentials: false\n```\n\nThis breaks `git push` from later steps. On GitHub, use `gh release\ncreate --target \"${GITHUB_SHA}\"` to create the tag and release via the\nAPI. On Gitea, use `tea releases create` or a direct API call with a\nscoped token. If you truly need `git push` (for example, to push a\ntag), scope the credentials to the single step that needs them —\ndon't leave them persistent for the whole job.\n\n`gh release create` creates the tag too when it doesn't exist yet, so a\nbuild workflow can cut its own release in one step. It needs `contents:\nwrite` and an explicit `GH_TOKEN` — the `gh` CLI does not pick up the\njob token on its own:\n\n```yaml\n- name: Create GitHub release\n  env:\n    GH_TOKEN: ${{ github.token }}\n    VERSION: ${{ github.event.inputs.version }}\n  run: |\n    gh release create \"v$VERSION\" \\\n      --target \"$GITHUB_SHA\" \\\n      --title \"v$VERSION\" \\\n      --notes \"Released from $GITHUB_SHA.\"\n```\n\nKeep backticks out of `--notes`. An unquoted heredoc or a double-quoted\nstring runs them as command substitution, and quoting the heredoc\ndelimiter to stop that also kills the variable expansion you wanted.\nWrite the notes without code spans, or build a notes file and pass\n`--notes-file`.\n\nIndirect environment variable expansion. Never interpolate expressions\ndirectly in `run:` scripts — an attacker-controlled value (branch\nname, PR title, issue body) can inject shell commands. Assign\nexpressions to env vars first:\n\n```yaml\n# wrong — injectable.\n- run: echo \"${{ github.event.pull_request.title }}\"\n\n# correct — safe expansion.\n- env:\n    PR_TITLE: ${{ github.event.pull_request.title }}\n  run: echo \"$PR_TITLE\"\n```\n\nName the env var after the expression path, uppercased with\nunderscores: `${{ steps.meta.outputs.version }}` →\n`STEPS_META_OUTPUTS_VERSION`, `${{ needs.build.outputs.image }}` →\n`NEEDS_BUILD_OUTPUTS_IMAGE`.\n\n## Concurrency\n\nCancel in-progress PR runs. Use the workflow name and ref as the\nconcurrency key, and only cancel for PRs (not pushes to main):\n\n```yaml\nconcurrency:\n  group: ${{ github.workflow }}-${{ github.ref }}\n  cancel-in-progress: ${{ github.event_name == 'pull_request' }}\n```\n\nSerialize deploys. Use a fixed group name with `cancel-in-progress:\ntrue` so only the latest deploy runs:\n\n```yaml\nconcurrency:\n  group: fly-deploy\n  cancel-in-progress: true\n```\n\n## Job structure\n\nSeparate test, build, and deploy. Use `needs:` to express dependencies\nand `if:` to gate jobs on context:\n\n```yaml\njobs:\n  test:\n    # runs on all pushes and PRs.\n  build:\n    needs: test\n    if: github.ref == 'refs\u002Fheads\u002Fmain' && github.event_name == 'push'\n  deploy:\n    needs: build\n    if: github.ref == 'refs\u002Fheads\u002Fmain' && github.event_name == 'push'\n```\n\nPass data between jobs with outputs. Declare outputs in the producing\njob and reference them downstream. Assign the output to an env var\nrather than interpolating in `run:`:\n\n```yaml\nbuild:\n  outputs:\n    image: ghcr.io\u002F${{ github.repository }}:${{ steps.meta.outputs.version }}\n\ndeploy:\n  needs: build\n  steps:\n    - run: flyctl deploy --image \"$IMAGE\"\n      env:\n        IMAGE: ${{ needs.build.outputs.image }}\n```\n\n## Environments (GitHub only)\n\nUse GitHub environments for deploy protection rules and\nenvironment-scoped secrets. For PR previews, key the name on the PR\nnumber:\n\n```yaml\npreview:\n  environment:\n    name: pr-${{ github.event.number }}\n    url: ${{ steps.deploy.outputs.url }}\n```\n\nGitea doesn't have a fully equivalent environments feature. For Gitea,\nuse repo-level or org-level secrets and gate sensitive jobs with `if:`\nconditions instead.\n\n## Zizmor\n\nStatic analysis for Actions workflows. Catches template injection,\nexcessive permissions, unpinned actions, credential leaks, and more.\nRun `zizmor --help` for full options. Zizmor treats Gitea and GitHub\nworkflows the same way — point it at both directories.\n\nAlways add a zizmor audit job to CI. For a repo with both directories,\npass them explicitly:\n\n```yaml\nzizmor:\n  runs-on: ubuntu-latest\n  permissions:\n    contents: read         # checkout.\n    security-events: write # upload SARIF to code scanning (GitHub only — drop on Gitea).\n  steps:\n    - uses: actions\u002Fcheckout@\u003Csha> # v6\n      with:\n        persist-credentials: false\n    - uses: zizmorcore\u002Fzizmor-action@\u003Csha>\n      with:\n        inputs: .gitea\u002Fworkflows\u002F* .github  # audit both sets.\n        advanced-security: false             # set true on GitHub for SARIF upload.\n        annotations: true\n```\n\nOn Gitea, drop `security-events: write` and the SARIF upload — leave\n`annotations: true` so findings show up in the run log.\n\nLocal usage. `zizmor .` only discovers `.github\u002Fworkflows\u002F` — pass\n`.gitea\u002Fworkflows\u002F*` explicitly on a dual-engine repo, or it silently\nskips every Gitea workflow:\n\n```bash\nzizmor .gitea\u002Fworkflows\u002F* .github   # audit both directories.\nzizmor .gitea\u002Fworkflows\u002Fci.yml      # single file.\nzizmor --fix .gitea\u002Fworkflows\u002F* .github\nzizmor --pedantic .gitea\u002Fworkflows\u002F* .github\n```\n\nConfigure with `zizmor.yml` in the repo root, `.github\u002F`, or\n`.gitea\u002F`. Ignore inline with a justification after `--`:\n\n```yaml\non:\n  workflow_run: # zizmor: ignore[dangerous-triggers] -- scoped to main branch, checks conclusion.\n```\n\n## Renovate integration\n\nOn GitHub, pin action SHAs and let Renovate update them. The\n`github-actions` manager detects `uses:` lines automatically — no\nextra config needed.\n\nOn Gitea, Renovate works but needs the workflow paths configured —\nits `github-actions` manager looks at `.github\u002Fworkflows\u002F` by default.\nExtend `fileMatch` in `renovate.json`:\n\n```json\n{\n  \"github-actions\": {\n    \"fileMatch\": [\"(^|\u002F)\\\\.gitea\u002Fworkflows\u002F[^\u002F]+\\\\.ya?ml$\"]\n  }\n}\n```\n\n## Quick reference\n\n| What | How |\n|---|---|\n| Set step output | `echo \"key=value\" >> \"$GITHUB_OUTPUT\"` |\n| Set env for later steps | `echo \"KEY=value\" >> \"$GITHUB_ENV\"` |\n| Conditional job | `if: github.ref == 'refs\u002Fheads\u002Fmain'` |\n| Conditional step | `if: github.event.action != 'closed'` |\n| Job dependency | `needs: [test, lint]` |\n| Job output | `outputs: { version: ${{ steps.x.outputs.version }} }` |\n| Consume job output | `${{ needs.build.outputs.version }}` |\n| Cancel previous runs | `cancel-in-progress: true` in `concurrency:` |\n| Required permissions | `permissions:` block per job |\n| GitHub CLI in a step | `env: { GH_TOKEN: ${{ github.token }} }` |\n| Gitea CLI in a step | `env: { TEA_TOKEN: ${{ secrets.TEA_TOKEN }} }` |\n",{"name":5,"description":7},"main","54400d2fb3ebb925baf35311c647aaa31e7a5222","ai\u002Fskills\u002Factions-workflows",0,"https:\u002F\u002Fgithub.com\u002Fkejadlen\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002Fkejadlen","https:\u002F\u002Fkejadlen.dev","2026-11-14 03:39:37",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kejadlen\u002Fdotfiles --skill actions-workflows",{"tool":38,"command":39},"bunx","bunx skills add kejadlen\u002Fdotfiles --skill actions-workflows",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kejadlen\u002Fdotfiles --skill actions-workflows","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkejadlen\u002Fdotfiles\u002Fblob\u002Fmain\u002Fai\u002Fskills\u002Factions-workflows\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7DEVM19CB8GSCZV56PHA594","zoekt","Use when searching code across repositories — prefer zoekt over grep\u002Fripgrep for indexed code search. Covers indexing repos, search syntax, and query patterns.","https:\u002F\u002Fgithub.com\u002Fkejadlen\u002Fdotfiles\u002Fblob\u002Fmain\u002Fai\u002Fskills\u002Fzoekt\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7DEVF10JKR56RSX30PZ8BNH","writing-for-accessibility","Use when writing documentation, alt text, diagrams, or any content that should be accessible to people with disabilities. Covers alt text, color contrast, inclusive language, and accessible visuals. Also use when reviewing documents for accessibility.","https:\u002F\u002Fgithub.com\u002Fkejadlen\u002Fdotfiles\u002Fblob\u002Fmain\u002Fai\u002Fskills\u002Fwriting-for-accessibility\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7DEVA0Q63VMQWG32VN18XYB","writing-error-messages","Use when writing, reviewing, or improving error messages in code, CLI tools, APIs, or UIs. Covers identifying the cause, explaining the fix, and setting the right tone. Also use when error messages are vague, unactionable, or confusing.","https:\u002F\u002Fgithub.com\u002Fkejadlen\u002Fdotfiles\u002Fblob\u002Fmain\u002Fai\u002Fskills\u002Fwriting-error-messages\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7DEV6GGF2H3FW3YCPWXRRT6","working-in-the-open","Use when making design decisions during implementation — routes rationale to the right venue (commits, task comments, code comments, or documentation) based on how durable the context needs to be","https:\u002F\u002Fgithub.com\u002Fkejadlen\u002Fdotfiles\u002Fblob\u002Fmain\u002Fai\u002Fskills\u002Fworking-in-the-open\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7DEV2XTM37B9S0QV8X9SNSW","web-standards","Use when writing or reviewing HTML, CSS, or browser JavaScript — covers semantic markup, native platform features over libraries, Baseline browser support, accessibility and APCA contrast, and optional validation with vnu, axe, and Lighthouse","https:\u002F\u002Fgithub.com\u002Fkejadlen\u002Fdotfiles\u002Fblob\u002Fmain\u002Fai\u002Fskills\u002Fweb-standards\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7DETYVQNPNGXC094DT0PTDF","web-design","Use when designing or building web UI, frontends, or styling — covers personal web design preferences, fluid layout, and Alpine.js","https:\u002F\u002Fgithub.com\u002Fkejadlen\u002Fdotfiles\u002Fblob\u002Fmain\u002Fai\u002Fskills\u002Fweb-design\u002FSKILL.md",[],[]]