New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Linear Security Basics

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

Harden Linear credentials, OAuth, team access, webhook verification, logging, and rotation.

MITAuto-check passedBackend & APIs

Install Linear Security Basics

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-security-basics -a claude-code

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace linear-security-basics --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/linear-security-basics .claude/skills/linear-security-basics && 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
linear-security-basics
GitHub stars
2.8k
Token cost
~1.3k tokens
SKILL.md length
503 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Harden Linear credentials, OAuth, team access, webhook verification, logging, and rotation.

  • Works in 6 steps: Inventory tokens, client and signing… → Select the narrowest auth actor and… → Verify webhook raw-body HMAC before… → …
  • Threat-modeling an integration
  • SKILL.md covers Overview, Prerequisites, Tool Discipline and Current Contract, plus 7 more sections
  • Needs API_KEY and ACCESS_TOKEN

What it does

Linear Security Basics is an agent skill from jeremylongshore/tons-of-skills-marketplace. Harden Linear credentials, OAuth, team access, webhook verification, logging, and rotation. Use when threat-modeling an integration or correcting a security gap. Trigger with "secure Linear integration", "review Linear OAuth security", or "verify Linear webhooks".

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Designed for Claude Code; live verification requires network access and an approved Linear workspace credential

It sits in Backend & APIs, covering Webhooks, OAuth and OpenID Connect and Threat modeling. 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

  • Threat-modeling an integration
  • Correcting a security gap
  • With secure Linear integration
  • Review Linear OAuth security

Example prompts

  • “secure Linear integration”
  • “review Linear OAuth security”
  • “verify Linear webhooks”
  • “/linear-security-basics”

Requirements

  • A credential in API_KEY
  • A credential in ACCESS_TOKEN
  • Compatibility (from SKILL.md): Designed for Claude Code; live verification requires network access and an approved Linear workspace credential
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, Write, Edit

Workflow steps

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

  1. Inventory tokens, client and signing secrets, redirect URLs, scopes, team access, caches, logs, exports, and third-party processors.
  2. Select the narrowest auth actor and scopes, validate OAuth state/PKCE, and store credentials only in an approved secret manager.
  3. Verify webhook raw-body HMAC before parsing or queuing; reject invalid signatures and stale/replayed deliveries.
  4. Redact authorization, cookies, queries, variables, issue content, emails, actor data, and signatures from telemetry.
  5. Test revocation, client-secret rotation, signing-secret rotation, compromised-token containment, and app disablement.
  6. Document residual risk, accountable owners, and an independently approved remediation rollout.

What it can do on your machine

Read from SKILL.md and the folder at commit 80f86df. 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):

    • linear.app

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

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • API_KEY
    • ACCESS_TOKEN

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

  • Compatibility

    Designed for Claude Code; live verification requires network access and an approved Linear workspace credential

    From compatibility in the SKILL.md frontmatter.

Context cost

Linear Security Basics loads about 1.3k tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 72 tokens; SKILL.md has 503 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~72
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.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 80f86df, republished under its MIT licence (© jeremylongshore). 503 words, ~1,262 tokens.

Download SKILL.mdSave it as .claude/skills/linear-security-basics/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
linear-security-basics
description
Harden Linear credentials, OAuth, team access, webhook verification, logging, and rotation. Use when threat-modeling an integration or correcting a security gap. Trigger with "secure Linear integration", "review Linear OAuth security", or "verify Linear webhooks".
allowed-tools
Read, Glob, Grep, WebFetch, Write, Edit
compatibility
Designed for Claude Code; live verification requires network access and an approved Linear workspace credential
argument-hint
[repository-path] [auth|webhook|data|rotation]
version
1.13.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
tags
saas, linear, security
model
inherit
effort
high

Linear Integration Security Baseline

Overview

Apply least privilege and fail-closed verification across every credential, workspace boundary, inbound event, and diagnostic path.

Prerequisites

  • The target repository, Linear workspace, environment, and accountable owner
  • Current security, privacy, compliance, capacity, and change-control requirements
  • An approved Linear credential only when a bounded live verification is necessary

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, and evidence. Use WebFetch only for current first-party Linear documentation and package metadata. Use Write or Edit only for requested implementation with known target files. Never write credentials, customer content, unrestricted environment output, or unredacted GraphQL variables.

Current Contract

  • Authorization-code OAuth supports PKCE; applications must use exact registered redirect URLs and validate authorization state.
  • All OAuth apps moved to the refresh-token system on 2026-04-01; access and refresh tokens require secure server-side storage and revocation handling.
  • Webhook authenticity is HMAC-SHA256 over the exact raw body; compare safely and use timestamp/delivery ID for replay controls.
  • Client-secret rotation and webhook-signing-secret rotation are separate operations with different impacts.

Authentication

Use a personal API key only for owner-controlled scripts, OAuth with PKCE for user-delegated applications, or an enabled client-credentials grant for approved automation. Personal keys use Authorization: <API_KEY>; OAuth tokens use Authorization: Bearer <ACCESS_TOKEN>. Store credentials server-side in an approved secret manager.

Treat app approval, team access, scope changes, credential creation, rotation, revocation, and production access as owner-approved actions.

Instructions

  1. Inventory tokens, client and signing secrets, redirect URLs, scopes, team access, caches, logs, exports, and third-party processors.
  2. Select the narrowest auth actor and scopes, validate OAuth state/PKCE, and store credentials only in an approved secret manager.
  3. Verify webhook raw-body HMAC before parsing or queuing; reject invalid signatures and stale/replayed deliveries.
  4. Redact authorization, cookies, queries, variables, issue content, emails, actor data, and signatures from telemetry.
  5. Test revocation, client-secret rotation, signing-secret rotation, compromised-token containment, and app disablement.
  6. Document residual risk, accountable owners, and an independently approved remediation rollout.
Show full SKILL.md (184 more words)Show less

Approval Boundaries

Do not create, reveal, rotate, or revoke credentials; authorize an OAuth app; change scopes or team access; create, mutate, archive, or delete workspace data; configure or re-enable webhooks; import or export data; change roles, SCIM, or audit streaming; transmit diagnostics; change paid entitlements; or perform another production mutation without explicit approval from the accountable owner. Keep diagnosis read-only unless implementation was requested.

Output

Return the workspace and team scope, auth mode without credential value, files and contracts inspected, exact operation names, evidence collected, validation result, sensitive fields redacted, remaining risk, accountable owner, approval state, and rollback or next action.

Error Handling

ConditionResponse
Token exposedRevoke or rotate the affected credential, scrub retained copies, and audit access.
Signature invalidReject before parsing business data and preserve only redacted delivery metadata.
OAuth state mismatchAbort the flow; do not exchange the code.
Scope too broadReduce scopes/team access and reauthorize through the approved change path.

Examples

Use a compact handoff that makes scope, mutation authority, and verification evidence reviewable.

Input:

text
auth=oauth-pkce; scopes=read,write; teams=approved-subset; raw-body=true

Expected handoff:

text
threat-model=updated; secrets=server-side; replay-control=delivery-id+timestamp

Resources

© 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

SKILL.md and 1 other file (references) in skills/.curated/linear-security-basics of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit 80f86df

Compare with similar skills

Linear Security Basics 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.

Linear Security Basics compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Linear Security Basics this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.3kAutomated safety check: PassMIT
Security Threat Modelingdevcodex-labs/devcodex439—~771Automated safety check: PassAGPL-3.0
Stripe Best Practiceskanchengw/cnllm1752 repos~925Automated safety check: PassApache-2.0
Discord Php Bot Securitydiscord-php/DiscordPHP1.1k—~1.2kAutomated safety check: NotesMIT
GitHub OAuth Nango IntegrationAgentWorkforce/relay8671 repos~3.4kAutomated safety check: PassApache-2.0
Add OAuth Integrationrome-os/rome737—~3.6kAutomated safety check: PassMIT

Similar skills

  • Security Threat Modeling

    devcodex-labs/devcodex

    安全威胁建模专家 Owner — 当任务涉及权限、认证、授权、输入输出信任边界、密钥策略、审计、攻击面、Webhook/OAuth、敏感操作或用户要求安全专家视角时使用；要求识别滥用路径并绑定缓解验证。

    439 GitHub stars~771 tokensUpdated 23 days ago
    Backend & APIsAuto-check passed

  • Stripe Best Practices

    kanchengw/cnllm

    Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial…

    175 GitHub starsUsed in 2 repos~925 tokens
    Backend & APIsAuto-check passed

  • Discord Php Bot Security

    discord-php/DiscordPHP

    Audit checklist for DiscordPHP bots and API libraries — stop the bot token leaking to third-party APIs or logs, keep secrets out of customids and exception messages, use constant-time comparison and…

    1.1k GitHub stars~1.2k tokensUpdated 3 days ago
    Backend & APIsAuto-check: notes

  • GitHub OAuth Nango Integration

    AgentWorkforce/relay

    A skill your agent uses when implementing GitHub OAuth + GitHub App authentication with Nango - provides two-connection pattern for user login and repo access with webhook handling

    867 GitHub starsUsed in 1 repo~3.4k tokens
    Backend & APIsAuto-check passed

  • Add OAuth Integration

    rome-os/rome

    Add a new Rome-managed OAuth integration for a third-party service so a user can delegate access by clicking Connect, and Rome can act on the service with the delegated token (the GitHub/Slack model…

    737 GitHub stars~3.6k tokensUpdated today
    Backend & APIsAuto-check passed

  • Triggers Guide

    OtoDock/oto-dock

    Reference for the triggers-mcp tools — the trigger↔task and trigger↔notification patterns with full call shapes, vendor-subscribed (OAuth) triggers and eventfilter rules, payload placeholders…

    190 GitHub stars~3k tokensUpdated 2 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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    Auto-check passed

Categories

Questions about Linear Security Basics

What does Linear Security Basics do?

Harden Linear credentials, OAuth, team access, webhook verification, logging, and rotation. Linear Security Basics is an agent skill from jeremylongshore/tons-of-skills-marketplace. Harden Linear credentials, OAuth, team access, webhook verification, logging, and rotation.

When should I use Linear Security Basics?

Linear Security Basics fits situations like: threat-modeling an integration; correcting a security gap; with secure Linear integration; review Linear OAuth security.

How do I install Linear Security Basics in Claude Code?

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

How do I install Linear Security Basics in Codex?

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

Can I use Linear Security Basics 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 linear-security-basics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linear-security-basics, .gemini/skills/linear-security-basics, .github/skills/linear-security-basics and .opencode/skills/linear-security-basics in your project.

What does Linear Security Basics need to run?

Going by SKILL.md and its folder, Linear Security Basics needs credentials named API_KEY and ACCESS_TOKEN. Our summary lists: A credential in API_KEY; A credential in ACCESS_TOKEN. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebFetch, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; live verification requires network access and an approved Linear workspace credential.

Does Linear Security Basics access the network?

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

Is Linear Security Basics 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 Linear Security Basics use?

Linear Security Basics 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 Linear Security Basics use?

About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 816 tokens, read only when the agent opens those files.

What are the alternatives to Linear Security Basics?

Skills that share tags, products or a category with Linear Security Basics: Security Threat Modeling (devcodex-labs/devcodex, 439 stars), Stripe Best Practices (kanchengw/cnllm, 175 stars), Discord Php Bot Security (discord-php/DiscordPHP, 1.1k stars) and GitHub OAuth Nango Integration (AgentWorkforce/relay, 867 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Linear Security Basics?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,825 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 9, 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.