Syncable Entity Integration Tests
twentyhq/twenty
Step-by-step guide to writing the mandatory integration tests for syncable metadata entities in Twenty's server, covering failures and CRUD success cases.
Design Linear-aware CI checks without turning every build into an uncontrolled production mutation.
Install Linear CI Integration
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-ci-integration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace linear-ci-integration --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-ci-integration .claude/skills/linear-ci-integration && rm -rf skills-srcUse ~/.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/
Install the "linear-ci-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/linear-ci-integration into .claude/skills/linear-ci-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-ci-integration", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/linear-ci-integrationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-ci-integration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace linear-ci-integration --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/linear-ci-integration .agents/skills/linear-ci-integration && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "linear-ci-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/linear-ci-integration into .agents/skills/linear-ci-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-ci-integration", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-ci-integration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace linear-ci-integration --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/linear-ci-integration .cursor/skills/linear-ci-integration && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "linear-ci-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/linear-ci-integration into .cursor/skills/linear-ci-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-ci-integration", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/linear-ci-integration--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-ci-integration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace linear-ci-integration --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/linear-ci-integration .gemini/skills/linear-ci-integration && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "linear-ci-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/linear-ci-integration into .gemini/skills/linear-ci-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-ci-integration", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace linear-ci-integrationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-ci-integration -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/linear-ci-integration .github/skills/linear-ci-integration && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "linear-ci-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/linear-ci-integration into .github/skills/linear-ci-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-ci-integration", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-ci-integration -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace linear-ci-integration --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/linear-ci-integration .opencode/skills/linear-ci-integration && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "linear-ci-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/linear-ci-integration into .opencode/skills/linear-ci-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linear-ci-integration", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
linear-ci-integration- GitHub stars
- 2.8k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 532 words
- Files
- 2 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design Linear-aware CI checks without turning every build into an uncontrolled production mutation.
- Works in 6 steps: Inventory existing CI, test doubles,… → Keep pull-request tests offline with… → Put any live read probe in a separately… → …
- Validating a Linear adapter
- SKILL.md covers Overview, Prerequisites, Tool Discipline and Current Contract, plus 7 more sections
- Needs API_KEY and ACCESS_TOKEN
What it does
Linear CI Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Design Linear-aware CI checks without turning every build into an uncontrolled production mutation. Use when validating a Linear adapter, obtaining a short-lived automation token, or linking CI evidence to work. Trigger with "test Linear in CI", "add Linear contract tests", or "authenticate Linear automation".
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 Integration testing. It works with GraphQL. 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
- Validating a Linear adapter
- Obtaining a short-lived automation token
- Linking CI evidence to work
- With test Linear in CI
Example prompts
- “test Linear in CI”
- “add Linear contract tests”
- “authenticate Linear automation”
- “/linear-ci-integration”
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.
- Inventory existing CI, test doubles, secret providers, and any Linear-aware branch or pull-request convention.
- Keep pull-request tests offline with recorded, redacted GraphQL fixtures and schema-level assertions.
- Put any live read probe in a separately approved protected job; acquire the narrowest client-credentials token per run and never echo it.
- Gate live mutations behind an explicit environment approval and an idempotency key owned by the integration.
- Assert HTTP status, GraphQL errors, expected payload fields, and rate-limit headers; preserve only redacted receipts.
- Document who can rotate the OAuth client secret, disable the job, and clean up test artifacts.
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:
ReadGlobGrepWebFetchWriteEdit
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_KEYACCESS_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 CI Integration 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 83 tokens; SKILL.md has 532 words of instructions outside code blocks.
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). 532 words, ~1,274 tokens.
Download SKILL.mdSave it as
.claude/skills/linear-ci-integration/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- linear-ci-integration
- description
- Design Linear-aware CI checks without turning every build into an uncontrolled production mutation. Use when validating a Linear adapter, obtaining a short-lived automation token, or linking CI evidence to work. Trigger with "test Linear in CI", "add Linear contract tests", or "authenticate Linear automation".
- 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] [contract-test|client-credentials|issue-linking]
- version
- 1.13.0
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- tags
- saas, linear, ci-integration
- model
- inherit
- effort
- high
Linear CI Contract Integration
Overview
Add deterministic CI coverage around a Linear integration while keeping ordinary pull-request tests offline and production writes explicitly gated.
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
- For CI and scheduled automation, Linear recommends requesting a client-credentials token at the start of each run instead of persisting an access token as a long-lived key.
- A client-credentials token is an app-actor token, is valid for 30 days, and must be replaced after a 401; requesting different scopes revokes the app's existing app-actor tokens.
- GraphQL transport success does not prove operation success; CI assertions must inspect the response
errorsarray and mutation payload.
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
- Inventory existing CI, test doubles, secret providers, and any Linear-aware branch or pull-request convention.
- Keep pull-request tests offline with recorded, redacted GraphQL fixtures and schema-level assertions.
- Put any live read probe in a separately approved protected job; acquire the narrowest client-credentials token per run and never echo it.
- Gate live mutations behind an explicit environment approval and an idempotency key owned by the integration.
- Assert HTTP status, GraphQL
errors, expected payload fields, and rate-limit headers; preserve only redacted receipts. - Document who can rotate the OAuth client secret, disable the job, and clean up test artifacts.
Show full SKILL.md (192 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
| Condition | Response |
|---|---|
| Fixture/schema drift | Refresh from a redacted approved response and review the semantic change. |
| 401 in protected job | Discard the token, verify app access, and obtain a new per-run token. |
| GraphQL errors | Fail the job even when HTTP is 200; report code and path without sensitive variables. |
| Mutation may repeat | Stop and add an idempotency or reconciliation contract before retrying. |
Examples
Use a compact handoff that makes scope, mutation authority, and verification evidence reviewable.
Input:
mode=contract-test; live-probe=read-only; mutation-job=approval-gatedExpected handoff:
offline=pass; live-auth=separate; graphql-errors=checked; secrets=redactedResources
© 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-ci-integration of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- references/official-docs.md
Open the folder on GitHubat commit cfae287
Compare with similar skills
Linear CI Integration 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Linear CI Integration this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Syncable Entity Integration Teststwentyhq/twenty | 58k | — | ~3.4k | Automated safety check: Pass | Custom licence | |
| API Testingpetrkindlmann/qa-skills | 170 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Contract Testingpetrkindlmann/qa-skills | 170 | — | ~4.1k | Automated safety check: Pass | MIT | |
| API Testingcosmicstack-labs/mercury-agent-skills | 476 | — | ~449 | Automated safety check: Pass | MIT | |
| Integration Test GeneratorArabelaTso/Skills-4-SE | 253 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
API Testing
petrkindlmann/qa-skills
Test REST and GraphQL APIs with Playwright APIRequestContext, Supertest, or standalone HTTP clients.
Contract Testing
petrkindlmann/qa-skills
Implement consumer-driven contract testing with Pact-JS (v16).
API Testing
cosmicstack-labs/mercury-agent-skills
REST and GraphQL testing, Postman/Insomnia patterns, contract testing, schema validation, and monitoring
Integration Test Generator
ArabelaTso/Skills-4-SE
Generate integration tests for multiple interacting components in Python.
API Testing Patterns
proffesor-for-testing/agentic-qe
Comprehensive API testing patterns including contract testing, REST/GraphQL testing, and integration testing.
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming 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.
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.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
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.
Related
Works with
Categories
Questions about Linear CI Integration
What does Linear CI Integration do?
Design Linear-aware CI checks without turning every build into an uncontrolled production mutation. Linear CI Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Design Linear-aware CI checks without turning every build into an uncontrolled production mutation.
When should I use Linear CI Integration?
Linear CI Integration fits situations like: validating a Linear adapter; obtaining a short-lived automation token; linking CI evidence to work; with test Linear in CI.
How do I install Linear CI Integration in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-ci-integration -a claude-code`. Or copy the skill folder (skills/.curated/linear-ci-integration in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/linear-ci-integration in your project. Claude Code loads it when a task matches its description.
How do I install Linear CI Integration in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill linear-ci-integration -a codex`. Or copy the skill folder (skills/.curated/linear-ci-integration in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/linear-ci-integration in your project. Codex loads it when a task matches its description.
Can I use Linear CI Integration 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-ci-integration -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-ci-integration, .gemini/skills/linear-ci-integration, .github/skills/linear-ci-integration and .opencode/skills/linear-ci-integration in your project.
What does Linear CI Integration need to run?
Going by SKILL.md and its folder, Linear CI Integration 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 CI Integration 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 CI Integration 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 CI Integration use?
Linear CI Integration 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 CI Integration use?
About 1.3k tokens (SKILL.md is roughly 5.1k 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 CI Integration?
Skills that share tags, products or a category with Linear CI Integration: Syncable Entity Integration Tests (twentyhq/twenty, 58k stars), API Testing (petrkindlmann/qa-skills, 170 stars), Contract Testing (petrkindlmann/qa-skills, 170 stars) and API Testing (cosmicstack-labs/mercury-agent-skills, 476 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Linear CI Integration?
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.