github-secrets

Configure and diagnose GitHub Actions secrets and variables across organization, repository, and environment scopes.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/Sassy-Dog/sassydog-skills --skill github-secrets-sassy-dog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-secrets
Source: https://github.com/Sassy-Dog/sassydog-skills/tree/main/skills/github-secrets
Command: npx skills add https://github.com/Sassy-Dog/sassydog-skills --skill github-secrets-sassy-dog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? GitHub Actions secrets and variables fail silently when set at the wrong scope or referenced with the wrong context, producing empty values in CI with no error message. This Skill provides the scope hierarchy rules, CLI commands, and diagnostic workflow needed to set, list, and debug secrets and variables correctly. ## Core Features & Use Cases - Scope Management: Set and list secrets/variables at organization, repository, and environment levels using the correct gh secret and gh variable flags. - Context Disambiguation: Clarifies the difference between secrets.*, vars.*, env.*, and github.token workflow contexts so values resolve correctly. - Failure Diagnosis: A step-by-step checklist for debugging empty secret values, covering missing environment: declarations, scope shadowing, org visibility allow lists, and fork PR restrictions. - Use Case: A deploy workflow prints an empty PROD_DB_PASSWORD. Use this Skill to identify that the job is missing environment: production, add it, and verify the secret exists with gh secret list --env production. ## Quick Start Ask the agent to set the GitHub secret NPM_TOKEN at the repository level and verify it exists before updating the release workflow.

Frequently Asked Questions about github-secrets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set a GitHub Actions secret from the command line?

Use gh secret set NAME --body "value" for repository scope, adding --org ORG or --env ENV for organization or environment scopes. Variables use gh variable set with the same flags. Always check existence first with gh secret list or gh variable list.

What is the difference between GitHub secrets and variables?

Secrets (secrets.*) are encrypted, masked in logs, and write-only after creation; variables (vars.*) are plaintext and readable via CLI. Use secrets for tokens and passwords, variables for URLs and config flags. They are separate namespaces managed by gh secret and gh variable.

Why is my GitHub Actions secret empty in the workflow?

The most common cause is a missing environment: declaration on the job when using environment-level secrets. Other causes include wrong scope flags when setting, org secret visibility not including the repo, confusing secrets.X with vars.X, or fork PRs which never receive secrets.

Can I read the value of a GitHub secret after setting it?

No, GitHub secrets are write-only by design. There is no gh secret get command, and gh secret list shows names only. If the value is unknown, re-set it from the source of truth such as Doppler or a key vault.

Do repository secrets work for Dependabot pull requests?

No, Dependabot has its own secret scope and regular repository or organization secrets are not available to its PRs. Set Dependabot secrets explicitly with gh secret set NAME --app dependabot.