github-secrets

Manage GitHub repository, organization, and environment secrets via the GitHub API.

5|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/gabrielkoerich/skills --skill github-secrets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-secrets
Source: https://github.com/gabrielkoerich/skills/tree/main/github-secrets
Command: npx skills add https://github.com/gabrielkoerich/skills --skill github-secrets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

GitHub secrets management is essential for securing credentials used by CI/CD workflows. This skill provides a centralized CLI to manage repository, organization, and environment secrets via the GitHub API, including bulk imports and safe operations.

Core Features & Use Cases

  • List secrets across repositories, organizations, and environments with metadata
  • Add, update, and delete secrets with encryption
  • Bulk sync from JSON or .env files with dry-run and delete-missing options

Quick Start

Install Bun dependencies, then run the CLI to manage secrets for your GitHub projects.

Frequently Asked Questions about github-secrets

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

FAQPage Schema
How do I manage GitHub secrets across multiple repositories at scale?

You can manage GitHub secrets at scale by using a centralized CLI to interface with the GitHub API, enabling bulk syncing from JSON or .env files across repository, organization, and environment scopes with optional dry-run operations.

How does encryption work when adding or updating GitHub Actions secrets?

Encryption for GitHub Actions secrets is enforced by fetching and using repository public keys via the GitHub API before adding or updating credentials, ensuring sensitive workflow data is securely encrypted before storage.

Can I bulk sync environment secrets from a .env file to GitHub?

Yes, you can bulk sync environment secrets from a .env or JSON file to GitHub, utilizing dry-run options to preview changes and delete-missing flags to remove credentials that are no longer present in your local source file.

Do I need a GitHub token to list and delete organization secrets?

Yes, token-based authentication is required to list and delete organization secrets, providing the necessary API authorization to securely manage credentials and execute operations across your organization's repositories.

What is the safest way to delete missing GitHub secrets during a bulk sync?

The safest way to delete missing GitHub secrets during a bulk sync is to use a dry-run operation first, allowing you to preview which credentials will be removed by the delete-missing option before applying any actual changes to your repositories.