Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/clickup-install-auth

@820dfc8
Run it yourself

Configure ClickUp personal-token or OAuth authorization with server-side storage, state validation, Workspace verification, and rotation ownership. Use when connecting an application to ClickUp. Trigger with "ClickUp auth", "install ClickUp API", or "ClickUp OAuth setup".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/clickup-install-auth

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈74 tokens for metadata: the name and description. ≈863 when used: this file. ≈584 more on demand in 1 file.

Description uses 3.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈295 characters, or 3.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

ClickUp Authentication Setup

Overview

Choose the authentication mode by tenancy and ownership, then prove the authorized Workspace boundary without exposing credentials.

Prerequisites

  • A server-side application boundary and governed secret manager
  • For personal use/testing, an accountable ClickUp user; for public use, an owner/admin-created OAuth app
  • Exact redirect URIs, state storage, and an expected Workspace allow-list

Tool Discipline

Use Read, Glob, and Grep to inspect the repository, adapters, configuration names, tests, and evidence. Use WebFetch only for current official ClickUp documentation. Use Write or Edit after confirming the target file, Workspace boundary, and requested mode.

Current Contract

  • Personal tokens begin with pk_, are intended for individual/testing use, and do not expire unless regenerated or revoked.
  • User-facing integrations use OAuth Authorization Code at https://app.clickup.com/api and exchange at https://api.clickup.com/api/v2/oauth/token.
  • OAuth access tokens currently do not expire, but ClickUp marks that behavior subject to change.
  • Every API request includes the token in Authorization; authorized Workspaces are verified through the teams endpoint.

Authentication

Use a personal token only for accountable individual/testing work or OAuth Authorization Code for a user-facing integration. Inject the token server-side through a governed secret reference, send it in Authorization, verify authorized Workspace IDs, and never print the token, OAuth client secret, or webhook secret.

Instructions

  1. Choose personal or OAuth mode and record credential owner, environment, and intended Workspaces.
  2. Store token/client secret only in a secret manager and inject by reference at runtime.
  3. For OAuth, register exact HTTPS redirects, generate/validate state, and exchange each code server-side once.
  4. Call GET /api/v2/user and GET /api/v2/team with bounded timeouts.
  5. Compare authorized Workspace IDs with the allow-list and reject cross-tenant ambiguity.
  6. Document revocation/rotation, reauthorization, incident, and ownership-transfer procedures.

Approval Boundaries

Do not print tokens, put a client secret in frontend code, accept unvalidated state, silently expand Workspace authorization, or regenerate a shared token without owner approval.

Output

Return auth mode, secret-reference name, redirect/state result, authorized Workspace IDs in redacted form, verification status, and rotation owner.

Error Handling

Condition Response
State mismatch Reject the callback and start a new authorization attempt.
Redirect mismatch Correct the registered exact URI; do not relax validation.
Workspace not authorized Stop and require explicit user reauthorization.
Credential leaked Revoke/regenerate, scrub artifacts, and record the incident.

Examples

The example below is a redacted operator receipt; it contains no task text, member data, credential, or webhook secret.

mode=oauth; redirect=exact; state=valid; token=stored-by-reference; workspace-match=yes; writes=0

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides standard documentation and code examples for setting up ClickUp API authentication. It correctly implements security best practices, such as suggesting the use of .env files for secrets and .gitignore to prevent them from being committed to version control. No malicious behaviors or security vulnerabilities were detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 2 months ago
What it can do
Reads files Network Edits files
Modelinherit
argument-hint
[repository-path] [personal|oauth]
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "clickup",
  "authentication"
]
model
inherit
effort
high
compatibility
Designed for Claude Code; OAuth setup requires a ClickUp app owned by a Workspace owner or admin

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/clickup-install-auth