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

Interlinked

by QuentinCody in QuentinCody/interlinked-cli

Overview and router for the Interlinked CLI — a local guard, quality-enforcement, simplification-review, semantic-code-search, and observability layer for AI coding agents.

MITAuto-check passedDevOps & Cloud

Install Interlinked

skills CLI
$ npx skills add QuentinCody/interlinked-cli --skill interlinked -a claude-code

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

GitHub CLI
$ gh skill install QuentinCody/interlinked-cli interlinked --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/QuentinCody/interlinked-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/interlinked .claude/skills/interlinked && 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
interlinked
GitHub stars
178
Token cost
~4.1k tokens
SKILL.md length
1,613 words
Files
2
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Overview and router for the Interlinked CLI — a local guard, quality-enforcement, simplification-review, semantic-code-search, and observability layer for AI coding agents.

  • Works in 6 steps: When blocked, read the Suggestion: and… → Meet quality gates by improving code and… → [proven] findings are real — fix them;… → …
  • Tasks that involve Observability
  • SKILL.md covers The three surfaces, The .interlinked/ directory, What warnings mean: [proven]… and Where things run (server /…, plus 3 more sections
  • Calls python

What it does

Interlinked is an agent skill from QuentinCody/interlinked-cli. Overview and router for the Interlinked CLI — a local guard, quality-enforcement, simplification-review, semantic-code-search, and observability layer for AI coding agents. Load this when working in a repo that has a .interlinked/ directory, when you see any [interlinked:] output or a BLOCKED: … Suggestion: … reason and are not sure which area it belongs to, or when you need to know what the interlinked command can do. This skill explains the mental model, the .interlinked/ layout, the [proven]/[heuristic] tags…

Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in DevOps & Cloud, covering Observability, Codebase onboarding and Supply chain security. It works with Python. The repository describes itself as: The harness for your harness. Local hooks, taste enforcement, and developer observability for AI coding agents (Claude Code, Codex, Cursor, Copilot CLI). The licence is MIT.

When your agent uses it

  • Tasks that involve Observability
  • Tasks that involve Codebase onboarding
  • Tasks that involve Supply chain security

Example prompts

  • “/interlinked”

Requirements

  • Python 3

Workflow steps

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

  1. When blocked, read the Suggestion: and take the safe path — don't rewrite to dodge the pattern.
  2. Meet quality gates by improving code and behavioral evidence — simplify logic or extract cohesive responsibilities, verify relevant…
  3. [proven] findings are real — fix them; triage [heuristic] ones.
  4. Package installs are default-deny — surface an unapproved dep to the human, don't --force.
  5. Checkpoints/rewind mutate git — never run them without explicit per-turn authorization.
  6. Do not create worktrees — use the current workspace; ask a human operator to provision

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python

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

  • Network

    No URLs in SKILL.md.

    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.

Context cost

Interlinked loads about 4.1k tokens when it runs. Until then it costs about 188 tokens; SKILL.md has 1,613 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~188
When it runs · the whole SKILL.md, loaded when a task matches
~4.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 QuentinCody/interlinked-cli at commit 31b5259, republished under its MIT licence (© QuentinCody). 1,613 words, ~4,066 tokens.

Download SKILL.mdSave it as .claude/skills/interlinked/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
interlinked
description
Overview and router for the Interlinked CLI — a local guard, quality-enforcement, simplification-review, semantic-code-search, and observability layer for AI coding agents. Load this when working in a repo that has a `.interlinked/` directory, when you see any `[interlinked:*]` output or a `BLOCKED: … Suggestion: …` reason and are not sure which area it belongs to, or when you need to know what the `interlinked` command can do. This skill explains the mental model, the `.interlinked/` layout, the `[proven]`/`[heuristic]` tags, and routes you to the focused `interlinked-*` skill for setup, guard blocks, verify/checks, quality ratchets, simplification, local semantic indexing, supply-chain, spec-audit, observability, or coordination.

interlinked — overview & skill router

For repeated implementation advice (repeated_implementation), load interlinked-verify. This is an advisory AST comparison for Python and JS/TS, reported after a changeset and in the Stop/verification review. It is not a hard gate.

Use interlinked-verify for tests contracts import|inspect|run: portable executable examples, expected-value provenance and retained previous expectations. Use interlinked-spec-audit for preparing explicit documentation examples. Contract review is advisory; configured acceptance is separate from agent-authored proposals.

For provider edit normalization and Stop delivery, use interlinked-harness; for native qualification, use interlinked-setup; for re-entry/translation evidence, use interlinked-observability. Early test-readiness guidance is covered by interlinked-verify. Provider-specific capabilities remain available.

Use interlinked-verify for tests readiness and bounded tests review, including Python test setup and the distinction between tools present, assertions executed, and requirements covered. Use interlinked-simplification for the advisory Python cleanup/forwarding family.

Interlinked is a local control plane for AI coding agents. A local daemon ("the harness") hooks into Claude Code, Codex, Copilot CLI, Gemini CLI, Cursor, OpenCode, and Pi — and on every tool call the runner exposes to its hook surface it enforces deterministic policy (block/allow in milliseconds, no model in the decision path), fails closed on what causes incidents (destructive commands, secrets, unvetted deps), and writes a replayable local activity log. It is offline-first — no required cloud dependency or remote telemetry. Activity is recorded locally; an optional authenticated server provides multi-agent coordination and configured sync.

Runner registration is not a claim of identical native APIs. OpenCode and Pi use managed plugin/extension bridges and lack dedicated native MCP, subagent, and worktree lifecycle hooks; load interlinked-setup for activation/trust and interlinked-harness for ask/Stop behavior.

If you're an agent working in a repo with a .interlinked/ directory, you are being guarded by it. This skill orients you and points to the right focused skill.

The three surfaces

Jev semantic review is internal research only. The public Interlinked CLI has no jev command, and its harness never invokes Jev at Stop. Legacy jev guard settings do not enable it. Internal evaluation belongs to the source-checkout runner documented in docs/internal/jev.md; it is not a customer BYOK feature.

SurfaceRole
Interlinked CLI (interlinked …)Local hooks, guard, quality checks, activity capture, diagnostics.
Interlinked MCP ServerOptional remote source of truth for tasks, messages, reservations, agent state.
Web UI (/chat, /map)Optional human oversight and coordination.

The .interlinked/ directory

Everything is per-cwd under <repo>/.interlinked/. Key files:

FileGitPurpose
config.jsoncommittedserver URL, defaults, operational mode, feature flags
config.local.jsongitignoredtoken, agent name, workspace, sync mode
guard-rules.json / .local.jsonteam / localguard rules, file reminders, per-edit coverage/mutation policy
check-policy.json / .local.jsonteam / localreport-ratchet settings, including the mutation-score floor
lint-import.json, lint-baseline.jsonteamimported analyzer scopes/configuration digests and tighten-only existing-debt allowances
package-allowlist.jsoncommittedapproved dependencies (default-deny installs)
package-proposals/localpending dependency requests; never approval grants
verify-suppressions.jsoncommittedfile/glob check suppressions
test-dependencies.jsonteamadditive literal test-to-input dependency declarations
test-runs/localdurable pending requests, validated passing receipts, native reports and the last observed job
*-baseline.json, metric-caps.jsonmixedratchet water-lines (coverage/mutation/line-cap/caps); the daemon folds session evidence into three of them at SessionEnd, tighten-only — see interlinked-quality-gates
baseline-folds.jsonllocalaudit row per SessionEnd water-line fold (what tightened, what was refused)
hook-coverage.jsonlocaldaemon-owned protected/reserved file observations, pending versions, manual reviews and automated check receipts; writer identity remains unknown
mutation-manifest.jsonmixedstable per-mutant state for the live per-edit mutation ratchet
mutation-cloud-v3.local.jsongitignoredexperimental protocol-v3 endpoint, authority, key, runtime, and scheduler configuration
mutation-journal.sqlitelocalauthority-scoped durable mutation jobs, leases, authenticated evidence, manifest head, and outbox
mutation-findings.jsonllocalfsynced, deduplicated delivery records for durable background mutation findings
findings/corpus.jsonlcommitted-capablecommon finding storage, including recorded simplification extensions
findings/simplification-runs.jsonl, debt/manual-marker-snapshots.jsonllocalexplicit simplification-run and manual-marker snapshot receipts
semantic.json / .local.jsonteam / localoptional local semantic-index policy / machine runtime topology
index/functions/localgeneration-scoped function metadata and vectors; never synced
index/data/search.sqlite, data.config.jsonlocalrebuildable JSONL/archives search projection and bounded maintenance settings
capture-receipts.jsonl, capture-capabilities.jsonl, capture/state/localproducer write/availability evidence and derived lifecycle state
activity.jsonl, collection.jsonl, timeline.jsonllocalcaptured agent activity (enable gitignores the first two)
hook-runtime.jsonlocalpayload-free proof that each provider executed its current hook definition
harness.sock / harness.pid—the running daemon

What warnings mean: [proven] vs [heuristic]

Every message the harness sends you is tagged:

  • [proven] — a real compiler/linter/scanner/parser/test-runner produced it (tsc, biome, gitleaks, semgrep, …). Authoritative — fix it.
  • [heuristic] — a regex/AST-shape match that could be a false positive. Evaluate it.
  • No tag — an unknown check id (never guessed).

A block reason is always surfaced. Allow-time warnings are surfaced but easy to overlook (PreToolUse via additionalContext, PostToolUse via stderr) — read them.

Where things run (server / auth / offline)

CommandsServer neededWorks offline
enable, disable, doctor, verify, harness …, caps, simplify …, debt …, impact, allowlist, logs, statusnoyes
sync, watchyesno
tasks, send, inbox, handoff, workspaceyes (auth)no
checkpoint, rewind, resume, guardnoyes
Show full SKILL.md (834 more words)Show less

Which skill to load for what

Route coverage check --lane e2e, e2e evidence refusals and coverage-e2e-baseline.json to interlinked-quality-gates. Route e2e scaffold and [interlinked:e2e-obligation] (both confined to the Interlinked checkout itself — a host repository never sees them) to interlinked-verify. Route project e2e policy (.interlinked/e2e-policy.json), tests e2e status|plan|run|check|qualify|scaffold, the adoption workflow tests e2e discover|surfaces|adopt|doctor, the completion gates tests e2e check --staged|--revision|--base|--gate, tests e2e gate install|status|uninstall, tests e2e ci, tests e2e policy replace, POLICY_WEAKENED, CI_RECEIPT_NOT_FRESH, tests e2e expectations …, [interlinked:e2e] and [interlinked:e2e-quality] lines to interlinked-verify: a scenario obligation clears only through a supervised tests e2e run receipt for the current input generation, never through a unit run, a green console line or a copied report. Transport receipt diagnostics (hook-transport.jsonl) belong to interlinked-harness.

For the experimental uploaded Cowork plugin, use interlinked-cowork and interlinked cowork capabilities --json. Cowork cloud hooks execute away from the host daemon. Native crash/timeout behavior can fail open; the coding-client claims above do not imply identical Cowork enforcement or Desktop Chat hooks.

For hook parity and provider limitations, use interlinked harness capabilities --json and interlinked-setup. For [interlinked:hook-coverage] NOT CHECKED after an external write, use interlinked-verify. A declared hook, an installed entry, an observed invocation and native enforcement are separate evidence.

SituationLoad
Installing / enabling Interlinked, connecting a coding client/hook, daemon down or zombie, doctor fails, config/modeinterlinked-setup
A Bash command or edit was BLOCKED; a sandbox/effect-residue warning; a [interlinked:*] warning; suppressionsinterlinked-harness
Running interlinked verify; a pre_block check blocked an edit; landing a cross-file refactor; scratch scriptsinterlinked-verify
Selecting tests, explaining invalidation/reuse, resuming deferred test work (tests plan/run/status), explicit TS/JS/Python/Rust/Go suites (tests suite)interlinked-verify; incremental coverage contracts: interlinked-quality-gates
[interlinked:hook-coverage] NOT CHECKED; verifying or reviewing pending file versions (harness coverage)interlinked-verify; daemon/capability diagnostics: interlinked-setup
Discovering/adopting lint configs, script aliases and CI/tasks (lint scan, lint import, lint check), native or declared SARIF adapters, isolated --only-selected --config tool=file profiles and hook/audit cadenceinterlinked-verify; baseline integrity and retirement: interlinked-quality-gates
Advisory file size, or blocked by a function-token / coverage / complexity / CRAP / mutation ratchet; configuring report, per-edit, or durable mutation cloud work; operating the mutation journal; "can't lower a baseline"; adopt; automatic obligation or manual marker debt; dead code (deadcode scan + --categorize deletion-safety buckets, per-edit dead_code_action)interlinked-quality-gates
Finding, reviewing, recording, or auditing opportunities to delete, replace, defer, or shrink code; simplify …; simplification coverage/evidence/deep handoffinterlinked-simplification
metrics score, catalog/explain/compare/corpus, behavioral receipts, gate reach, incremental coverage, or syntax-token counter migrationsinterlinked-quality-gates
Dense expressions, callback depth, metrics expressions, .interlinked/readability.jsoninterlinked-quality-gates; formatter adoption and lint import --gate errors --target …: interlinked-verify
Guard ownership changes, guard-prediction-protocol, predicted intent or reconciliation receiptsinterlinked-harness; shared mode configuration: interlinked-setup
metrics jit, commit-time [interlinked:jit] warnings, within-repo percentile ranks, complexity churn hotspots or directory spreadinterlinked-quality-gates
Installing a local embedding model; building, inspecting, searching, or repairing the optional function-vector indexinterlinked-semantic-index
An npm/pip/cargo/… install or manifest edit was blocked; the package allowlistinterlinked-supply-chain
Spec/doc facts, drift, invariants, review findings, doctest; [interlinked:spec-*]interlinked-spec-audit
Explain earlier work, investigate failed/missed checks or file/session history, assess capture gaps, search JSONL/archives with data scan, compare storage engines with data lab, retain logs, inspect data views, recurrence, viz, chain audit, evidence-classed impact, syncinterlinked-observability
Server-backed tasks/messages/reservations/handoff; local checkpoints (git-mutating!)interlinked-coordination
Distill AGENTS.md / CLAUDE.md guidance into enforced harness rulesenforce (/enforce)

Quick orientation

metrics diagnostics --profile js-ts|python provides separate verbosity/erosion censuses with overlap and absolute contributors. Route counting semantics and measurement gaps to interlinked-quality-gates; route simplify review --diagnostics js-ts|python and candidate review to interlinked-simplification. metrics diagnostics compare validates saved diagnostic scope and identity. These features add no hook gate or automatic scan cadence; Python uses an isolated, bounded stdlib parser.

bash
interlinked                 # guided human first run (posture + hooks + skills + daemon)
interlinked enable          # explicit/automation install primitive
interlinked status          # dashboard: sessions, recent activity, health
interlinked doctor          # is everything installed & the daemon answering?
interlinked harness status  # liveness: answering / ZOMBIE / not running
interlinked harness checks   # how many checks / rules are active
interlinked data status --json # is retained evidence indexed through the relevant events?
interlinked data health --json # what capture is observed, failed, or unmeasured?
interlinked --help          # full command list

harness status and doctor verify liveness by round-trip, not PID. A red ZOMBIE (process alive, nothing answering) means the guard is off — interlinked harness restart. For Codex, doctor also compares .codex/hooks.json with the last executed definition hash; review changed hooks through /hooks, then run a hooked action.

When prior evidence is relevant, load interlinked-observability and use its bundled investigation workflows. Check freshness, search a specific session/file/check, and verify supporting raw records. data scan --raw reads bounded JSONL/gzip without creating SQLite. Indexing is an explicit storage choice: import budgets are not disk limits. Both indexing and rotation automation default off and are independent. Enabled indexing runs at SessionEnd. Retain raw logs and archives indefinitely. Lossless rotation keeps history available through data search; ordinary live-tail readers have narrower scope.

Golden rules for an agent in a guarded repo

  1. When blocked, read the Suggestion: and take the safe path — don't rewrite to dodge the pattern.
  2. Meet quality gates by improving code and behavioral evidence — simplify logic or extract cohesive responsibilities, verify relevant behavior, and never lower a baseline. A lower complexity score alone does not prove a better solution.
  3. [proven] findings are real — fix them; triage [heuristic] ones.
  4. Package installs are default-deny — surface an unapproved dep to the human, don't --force.
  5. Checkpoints/rewind mutate git — never run them without explicit per-turn authorization.
  6. Do not create worktrees — use the current workspace; ask a human operator to provision an approved worktree when isolation is required. Listing and cleanup remain allowed.

© QuentinCody, 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 in skills/interlinked of QuentinCody/interlinked-cli.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 31b5259

Compare with similar skills

Interlinked 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.

Interlinked compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Interlinked this skillQuentinCody/interlinked-cli178—~4.1kAutomated safety check: PassMIT
Agent Kill Switchvivekchand/clawmetry425—~1.1kAutomated safety check: PassMIT
Clawmetry Selfcheckvivekchand/clawmetry425—~515Automated safety check: PassMIT
New Pluginapache/skywalking-python219—~3.3kAutomated safety check: PassApache-2.0
Speculative Namingsgl-project/sglang37k2 repos~1.6kAutomated safety check: PassApache-2.0
Logfire Instrumentationbasicmachines-co/basic-memory4.1k—~2.3kAutomated safety check: PassAGPL-3.0

Similar skills

  • Agent Kill Switch

    vivekchand/clawmetry

    Give the human an off switch and a cost meter for the coding agents on this machine, using ClawMetry.

    425 GitHub stars~1.1k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Clawmetry Selfcheck

    vivekchand/clawmetry

    Read your own agent telemetry from ClawMetry (waste, progress, cost) and act on it before finishing a task.

    425 GitHub stars~515 tokensUpdated today
    DevOps & CloudAuto-check passed

  • New Plugin

    apache/skywalking-python

    Scaffold a new SkyWalking Python instrumentation plugin with all required files (plugin code, tests, docker-compose, expected data, services)

    219 GitHub stars~3.3k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Speculative Naming

    sgl-project/sglang

    Naming conventions for SGLang speculative decoding identifiers.

    37k GitHub starsUsed in 2 repos~1.6k tokens
    DevOps & CloudAuto-check passed

  • Logfire Instrumentation

    basicmachines-co/basic-memory

    Adds Pydantic Logfire tracing, logging and metrics to Python, JavaScript or TypeScript and Rust projects, with the correct setup order and library extras.

    4.1k GitHub stars~2.3k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Plugin Test

    apache/skywalking-python

    Build Docker test images and run SkyWalking Python plugin/unit/e2e tests locally, mirroring the CI pipeline

    219 GitHub stars~2.3k tokensUpdated today
    DevOps & CloudAuto-check passed

More from QuentinCody/interlinked-cli

All 12 skills in this repo

  • Interlinked Cowork

    QuentinCody/interlinked-cli

    Package, test, and operate the experimental Interlinked Cowork plugin.

    178 GitHub stars~1.6k tokensUpdated 5 days ago
    Auto-check passed

  • Interlinked Coordination

    QuentinCody/interlinked-cli

    Coordinate with other agents/humans via the optional Interlinked MCP Server, and use local checkpoints & file reservations.

    178 GitHub stars~2.9k tokensUpdated 5 days ago
    Auto-check passed

  • Interlinked Observability

    QuentinCody/interlinked-cli

    Investigate agent activity and JSONL/gzip evidence. An agent skill from QuentinCody/interlinked-cli.

    178 GitHub stars~10k tokensUpdated 5 days ago
    Auto-check passed

  • Interlinked Semantic Index

    QuentinCody/interlinked-cli

    Install and operate Interlinked's optional local semantic function index.

    178 GitHub stars~1.7k tokensUpdated 5 days ago
    Auto-check passed

  • Interlinked Spec Audit

    QuentinCody/interlinked-cli

    Keep prose specs and design docs honest against the code using Interlinked's spec-audit system.

    178 GitHub stars~3.3k tokensUpdated 5 days ago
    Auto-check passed

  • Interlinked Supply Chain

    QuentinCody/interlinked-cli

    Respond to blocked package installs and manage the Interlinked supply-chain allowlist.

    178 GitHub stars~2.8k tokensUpdated 5 days ago
    Auto-check passed

Works with

Categories

Questions about Interlinked

What does Interlinked do?

Overview and router for the Interlinked CLI — a local guard, quality-enforcement, simplification-review, semantic-code-search, and observability layer for AI coding agents. Interlinked is an agent skill from QuentinCody/interlinked-cli. Overview and router for the Interlinked CLI — a local guard, quality-enforcement, simplification-review, semantic-code-search, and observability layer for AI coding agents.

When should I use Interlinked?

Interlinked fits situations like: tasks that involve Observability; tasks that involve Codebase onboarding; tasks that involve Supply chain security.

How do I install Interlinked in Claude Code?

Run `npx skills add QuentinCody/interlinked-cli --skill interlinked -a claude-code`. Or copy the skill folder (skills/interlinked in QuentinCody/interlinked-cli) into .claude/skills/interlinked in your project. Claude Code loads it when a task matches its description.

How do I install Interlinked in Codex?

Run `npx skills add QuentinCody/interlinked-cli --skill interlinked -a codex`. Or copy the skill folder (skills/interlinked in QuentinCody/interlinked-cli) into .agents/skills/interlinked in your project. Codex loads it when a task matches its description.

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

What does Interlinked need to run?

Going by SKILL.md and its folder, Interlinked needs the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Interlinked access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Interlinked 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 Interlinked use?

Interlinked is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Interlinked use?

About 4.1k tokens (SKILL.md is roughly 16k 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 Interlinked?

Skills that share tags, products or a category with Interlinked: Agent Kill Switch (vivekchand/clawmetry, 425 stars), Clawmetry Selfcheck (vivekchand/clawmetry, 425 stars), New Plugin (apache/skywalking-python, 219 stars) and Speculative Naming (sgl-project/sglang, 37k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Interlinked?

QuentinCody (a GitHub user) maintains it in QuentinCody/interlinked-cli, which has 178 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 2, 2026.

Source: QuentinCody/interlinked-cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.