Agent skill

Workhuman Install Auth

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Select and document the supported Workhuman access path for a customer tenant, including SSO, managed integrations, or customer-issued API credentials.

MITAuto-check passedBackend & APIs

Install Workhuman Install Auth

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill workhuman-install-auth -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace workhuman-install-auth --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/workhuman-install-auth .claude/skills/workhuman-install-auth && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
workhuman-install-auth
GitHub stars
2.8k
Token cost
~1k tokens
SKILL.md length
409 words
Files
1
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Select and document the supported Workhuman access path for a customer tenant, including SSO, managed integrations, or customer-issued API credentials.

  • Works in 7 steps: Record tenant, products, data classes,… → Classify the path as interactive SSO, a… → Re-fetch the applicable first-party… → …
  • Repairing an integration
  • SKILL.md covers Overview, Prerequisites, Tool Discipline and Current Contract, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Workhuman Install Auth is an agent skill from jeremylongshore/tons-of-skills-marketplace. Select and document the supported Workhuman access path for a customer tenant, including SSO, managed integrations, or customer-issued API credentials. Use when onboarding or repairing an integration. Trigger with "configure Workhuman access".

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Designed for Claude Code; tenant access, identity changes, managed integrations, and credential issuance require customer and Workhuman authorization

It sits in Backend & APIs, covering Authentication. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Repairing an integration
  • With configure Workhuman access

Example prompts

  • “configure Workhuman access”
  • “/workhuman-install-auth”

Requirements

  • Compatibility (from SKILL.md): Designed for Claude Code; tenant access, identity changes, managed integrations, and credential issuance require customer and Workhuman authorization
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, Write, Edit

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Record tenant, products, data classes, intended reads and writes, environments, and accountable owners.
  2. Classify the path as interactive SSO, a Workhuman-managed integration, or a customer-issued API contract.
  3. Re-fetch the applicable first-party product page and the customer's current implementation documentation.
  4. Build an access matrix covering principal, roles or scopes, expiry, rotation, revocation, and break-glass ownership.
  5. Search the repository for guessed hosts, undocumented routes, hard-coded secrets, and mixed-tenant configuration.
  6. Present every tenant setting, connector enablement, consent, and credential request for explicit approval.
  7. After authorized provisioning, run the smallest documented read-only check and retain only redacted status and correlation evidence.

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • WebFetch
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • workhuman.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code; tenant access, identity changes, managed integrations, and credential issuance require customer and Workhuman authorization

    From compatibility in the SKILL.md frontmatter.

Context cost

Workhuman Install Auth loads about 1k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 409 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~67
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 409 words, ~1,049 tokens.

Download SKILL.mdSave it as .claude/skills/workhuman-install-auth/SKILL.md (or your agent's skills folder).
name
workhuman-install-auth
description
Select and document the supported Workhuman access path for a customer tenant, including SSO, managed integrations, or customer-issued API credentials. Use when onboarding or repairing an integration. Trigger with "configure Workhuman access".
allowed-tools
Read, Glob, Grep, WebFetch, Write, Edit
compatibility
Designed for Claude Code; tenant access, identity changes, managed integrations, and credential issuance require customer and Workhuman authorization
argument-hint
[tenant] [integration-purpose]
version
1.4.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
tags
saas, workhuman, authentication, sso, integration
model
inherit
effort
medium

Workhuman Tenant Access and Integration Onboarding

Overview

Choose the supported access model, establish ownership, and prove the smallest safe capability without guessing a host, route, grant, or credential format.

Prerequisites

  • The customer tenant, subscribed products, program owner, and integration purpose
  • Identity, security, data, and support owners for the affected workforce records
  • Current customer-authorized Workhuman documentation or an assigned Workhuman implementation contact

Tool Discipline

Use Read, Glob, and Grep to inspect local configuration, WebFetch to re-check first-party public and authorized tenant contracts, and Write or Edit only for secretless configuration and redacted evidence.

Current Contract

Workhuman publicly documents SSO, controlled privileges, an open API, and managed integrations such as Microsoft Teams and Workday. Its public pages do not define one universal API host, OAuth flow, scope set, or verification route; obtain those details from the customer's current contract.

Authentication

Separate interactive SSO, managed-connector authorization, and API credentials. Do not reuse browser sessions, infer client_credentials, copy administrator cookies, or put secrets in files, commands, prompts, logs, or receipts.

Instructions

  1. Record tenant, products, data classes, intended reads and writes, environments, and accountable owners.
  2. Classify the path as interactive SSO, a Workhuman-managed integration, or a customer-issued API contract.
  3. Re-fetch the applicable first-party product page and the customer's current implementation documentation.
  4. Build an access matrix covering principal, roles or scopes, expiry, rotation, revocation, and break-glass ownership.
  5. Search the repository for guessed hosts, undocumented routes, hard-coded secrets, and mixed-tenant configuration.
  6. Present every tenant setting, connector enablement, consent, and credential request for explicit approval.
  7. After authorized provisioning, run the smallest documented read-only check and retain only redacted status and correlation evidence.
Show full SKILL.md (138 more words)Show less

Approval Boundaries

Do not change SSO, assign privileges, enable an integration, issue credentials, or test production writes without the relevant customer and vendor owners.

Output

Return the selected access path, contract evidence, access matrix, secretless configuration, verification receipt, rotation and revocation owners, and unresolved vendor questions.

Error Handling

ConditionResponse
Customer API documentation is unavailableStop at the decision record and request it from the program owner or Workhuman.
SSO succeeds but an integration failsDiagnose the connector or API principal independently; do not reuse the browser session.
Capability is not subscribedRecord the entitlement gap and route it to the commercial or program owner.

Example

A redacted completion receipt might look like this:

text
tenant=customer-specific; path=managed-workday; principal=vendor-managed; contract=current; smoke=read-only-pass; secrets=redacted

Resources

Next Steps

Test reauthorization or credential rotation in a non-production context and assign a contract review date.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/.curated/workhuman-install-auth of jeremylongshore/tons-of-skills-marketplace.

Open the folder on GitHubat commit cfae287

Compare with similar skills

Workhuman Install Auth next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Workhuman Install Auth compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workhuman Install Auth this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1kAutomated safety check: PassMIT
Fortify Developmentcoollabsio/coolify63k4 repos~1.9kAutomated safety check: PassMIT
Supabase Development and Debuggingsupabase/agent-skills2.7k3 repos~3.6kAutomated safety check: PassMIT
Better Auth Best Practiceslatitude-dev/latitude-llm4.7k7 repos~1.6kAutomated safety check: PassMIT
Gitnexus Exploringaws-samples/sample-kolya-br-proxy10612 repos~749Automated safety check: PassMIT-0
Supabasecurvenote/curvenote1705 repos~2.2kAutomated safety check: PassCustom licence

Similar skills

  • Fortify Development

    coollabsio/coolify

    ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 4 repos~1.9k tokens
    Backend & APIsAuto-check passed
  • Official

    General Supabase skill for database, auth, Edge Functions, Realtime and storage work, plus client libraries, migrations, security audits, debugging and reading logs.

    2.7k GitHub starsUsed in 3 repos~3.6k tokens
    Backend & APIsAuto-check passed
  • Better Auth Best Practices

    latitude-dev/latitude-llm

    Configure Better Auth server and client, set up database adapters, manage sessions, add plugins, and handle environment variables.

    4.7k GitHub starsUsed in 7 repos~1.6k tokens
    Backend & APIsAuto-check passed
  • Gitnexus Exploring

    aws-samples/sample-kolya-br-proxy

    Official

    A skill your agent uses when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase.

    106 GitHub starsUsed in 12 repos~749 tokens
    Backend & APIsAuto-check passed
  • Supabase

    curvenote/curvenote

    A skill your agent uses when doing ANY task involving Supabase.

    170 GitHub starsUsed in 5 repos~2.2k tokens
    Backend & APIsAuto-check passed
  • Gemini Live API Dev

    google-gemini/gemini-skills

    Official

    A skill your agent uses when building real-time, bidirectional streaming applications with the Gemini Live API, or migrating legacy Live models (2.0/2.5/3.1) to Gemini 3.8 Live.

    4.3k GitHub stars~4.6k tokensUpdated 4 days ago
    Backend & APIsAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Workhuman Install Auth

What does Workhuman Install Auth do?

Select and document the supported Workhuman access path for a customer tenant, including SSO, managed integrations, or customer-issued API credentials. Workhuman Install Auth is an agent skill from jeremylongshore/tons-of-skills-marketplace. Select and document the supported Workhuman access path for a customer tenant, including SSO, managed integrations, or customer-issued API credentials.

When should I use Workhuman Install Auth?

Workhuman Install Auth fits situations like: repairing an integration; with configure Workhuman access.

How do I install Workhuman Install Auth in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill workhuman-install-auth -a claude-code`. Or copy the skill folder (skills/.curated/workhuman-install-auth in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/workhuman-install-auth in your project. Claude Code loads it when a task matches its description.

How do I install Workhuman Install Auth in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill workhuman-install-auth -a codex`. Or copy the skill folder (skills/.curated/workhuman-install-auth in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/workhuman-install-auth in your project. Codex loads it when a task matches its description.

Can I use Workhuman Install Auth in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill workhuman-install-auth -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workhuman-install-auth, .gemini/skills/workhuman-install-auth, .github/skills/workhuman-install-auth and .opencode/skills/workhuman-install-auth in your project.

What does Workhuman Install Auth need to run?

SKILL.md names no scripts, command-line tools or credentials: Workhuman Install Auth is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebFetch, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; tenant access, identity changes, managed integrations, and credential issuance require customer and Workhuman authorization.

Does Workhuman Install Auth access the network?

SKILL.md names 1 domain. As links in the text: workhuman.com. This is read from the text; nothing was executed.

Is Workhuman Install Auth safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Workhuman Install Auth use?

Workhuman Install Auth is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Workhuman Install Auth use?

About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Workhuman Install Auth?

Skills that share tags, products or a category with Workhuman Install Auth: Fortify Development (coollabsio/coolify, 63k stars), Supabase Development and Debugging (supabase/agent-skills, 2.7k stars), Better Auth Best Practices (latitude-dev/latitude-llm, 4.7k stars) and Gitnexus Exploring (aws-samples/sample-kolya-br-proxy, 106 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workhuman Install Auth?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.