credential-setup

Detect, configure, and verify GitHub authentication credentials for StatsClaw workflows.

89|17|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/statsclaw/statsclaw --skill credential-setup-statsclaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: credential-setup
Source: https://github.com/statsclaw/statsclaw/tree/main/skills/credential-setup
Command: npx skills add https://github.com/statsclaw/statsclaw --skill credential-setup-statsclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious, error-prone manual work of configuring GitHub authentication (PATs, SSH keys, etc.) before running statistical package development workflows, removing a common onboarding barrier for users and preventing workflow failures due to missing credentials.

Core Features & Use Cases

  • Multi-Method Credential Detection: Automatically checks for valid GitHub credentials via environment variables, gh CLI authentication, SSH keys, and git credential helpers in order of reliability.
  • Secure Configuration: Sets up git remote URLs and gh CLI authentication for the target repository, with security guidance to avoid plaintext token storage where possible.
  • Pre-Workflow Verification: Performs a hard gate check for push access to the target repository to catch credential issues before any code changes or pushes are attempted.
  • Use Case: A researcher running a StatsClaw workflow to fix a bug in their Python statistical package does not need to stop and manually configure GitHub credentials—this Skill handles all authentication setup automatically in the background.

Quick Start

Invoke the credential-setup skill at the start of any StatsClaw workflow targeting a GitHub repository to automatically detect, configure, and verify GitHub authentication credentials without any user intervention.

Frequently Asked Questions about credential-setup

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

FAQPage Schema
How do I automate GitHub authentication setup for statistical package development workflows?

Pre-workflow credential verification checks for push access to target GitHub repositories before any code changes are attempted, catching authentication issues early and preventing workflow failures during statistical package development.

Does workflow automation support gh CLI authentication and SSH keys for GitHub repositories?

If GitHub authentication fails, the credential setup process provides clear error messaging indicating which credential sources were checked, allowing users to diagnose missing environment variables, expired gh CLI tokens, or invalid SSH keys.

What is the best way to verify GitHub credentials before running git workflow automation?

The best way to verify GitHub credentials is performing a hard gate check for push access to the target repository, ensuring environment variables, gh CLI, SSH keys, or git credential helpers are valid before workflow execution begins.

Why does my GitHub authentication fail when pushing from an automated workflow?

GitHub authentication fails when none of the credential sources—environment variables, gh CLI, SSH keys, or git credential helpers—are valid or properly configured, triggering clear error messaging to guide corrective action.