Reproduce Chat States
different-ai/openwork
Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.
Run the smallest documented Linktree publish-and-verify workflow without inventing an API.
Install Linktree Hello World
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill linktree-hello-world -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace linktree-hello-world --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/linktree-hello-world .claude/skills/linktree-hello-world && 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 "linktree-hello-world" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/linktree-hello-world into .claude/skills/linktree-hello-world/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linktree-hello-world", 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/linktree-hello-worldType 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 linktree-hello-world -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace linktree-hello-world --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/linktree-hello-world .agents/skills/linktree-hello-world && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "linktree-hello-world" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/linktree-hello-world into .agents/skills/linktree-hello-world/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linktree-hello-world", 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 linktree-hello-world -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace linktree-hello-world --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/linktree-hello-world .cursor/skills/linktree-hello-world && 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 "linktree-hello-world" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/linktree-hello-world into .cursor/skills/linktree-hello-world/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linktree-hello-world", 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/linktree-hello-world--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 linktree-hello-world -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace linktree-hello-world --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/linktree-hello-world .gemini/skills/linktree-hello-world && 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 "linktree-hello-world" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/linktree-hello-world into .gemini/skills/linktree-hello-world/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linktree-hello-world", 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 linktree-hello-worldInstalls 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 linktree-hello-world -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/linktree-hello-world .github/skills/linktree-hello-world && 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 "linktree-hello-world" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/linktree-hello-world into .github/skills/linktree-hello-world/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linktree-hello-world", 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 linktree-hello-world -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 linktree-hello-world --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/linktree-hello-world .opencode/skills/linktree-hello-world && 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 "linktree-hello-world" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/linktree-hello-world into .opencode/skills/linktree-hello-world/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linktree-hello-world", 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
linktree-hello-world- GitHub stars
- 2.8k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 565 words
- Files
- 2 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run the smallest documented Linktree publish-and-verify workflow without inventing an API.
- Works in 7 steps: Confirm the authorized account, profile… → Inspect local campaign copy, destination… → In Linktree Admin, add one classic link… → …
- Launching a profile
- 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
Linktree Hello World is an agent skill from jeremylongshore/tons-of-skills-marketplace. Run the smallest documented Linktree publish-and-verify workflow without inventing an API. Use when launching a profile or proving a new Linktree setup. Trigger with "smoke test Linktree".
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 work requires an authorized Linktree account and approval from the profile, Workspace, data, or partner-integration owner
It sits in Testing & QA, covering QA and bug reports. 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
- Launching a profile
- Proving a new Linktree setup
- With smoke test Linktree
Example prompts
- “smoke test Linktree”
- “/linktree-hello-world”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code; live work requires an authorized Linktree account and approval from the profile, Workspace, data, or partner-integration owner
- Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, Write, Edit
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Confirm the authorized account, profile URL, approved destination, owner, rollback action, and test window.
- Inspect local campaign copy, destination inventory, and acceptance notes with Read, Glob, and Grep; do not search credential files.
- In Linktree Admin, add one classic link with an unambiguous title and the approved destination, leaving unrelated links unchanged.
- Open the public profile in a signed-out mobile viewport and desktop viewport; confirm title, placement, destination, HTTPS, and expected…
- Exercise one safe failure path with a deliberately unpublished draft or a nonproduction destination, then confirm visitors cannot reach it.
- Use Write or Edit to record a redacted receipt containing timestamps, expected and actual destination hosts, and rollback status.
- Use WebFetch only to recheck the current official Linktree guidance when UI labels or feature availability differ.
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
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.
Compatibility
Designed for Claude Code; live work requires an authorized Linktree account and approval from the profile, Workspace, data, or partner-integration owner
From compatibility in the SKILL.md frontmatter.
Context cost
Linktree Hello World loads about 1.3k tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 52 tokens; SKILL.md has 565 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). 565 words, ~1,260 tokens.
Download SKILL.mdSave it as
.claude/skills/linktree-hello-world/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- linktree-hello-world
- description
- Run the smallest documented Linktree publish-and-verify workflow without inventing an API. Use when launching a profile or proving a new Linktree setup. Trigger with "smoke test Linktree".
- allowed-tools
- Read, Glob, Grep, WebFetch, Write, Edit
- compatibility
- Designed for Claude Code; live work requires an authorized Linktree account and approval from the profile, Workspace, data, or partner-integration owner
- argument-hint
- [profile-url] [test-destination]
- version
- 1.8.0
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- tags
- saas, linktree, smoke-test, publishing, link-qa
- model
- inherit
- effort
- medium
Linktree First-Publish Smoke Test
Overview
Prove one bounded path from an approved destination to a visible classic link, then verify the visitor experience on mobile and desktop before broader promotion.
Prerequisites
- An authorized Linktree account or a clearly bounded design-only task
- The profile, Workspace, destination, campaign, data, or integration owner appropriate to the requested change
- Current account evidence for plan-dependent features and user-supplied approved partner documentation for every private interface
Tool Discipline
Use Read, Glob, and Grep to inspect repository specifications, sanitized fixtures, policies, tests, and prior receipts.
Use WebFetch only for current official Linktree documentation or explicitly approved partner documentation.
Use Write or Edit only after confirming scope, target, owners, data classification, and approval state. These tools do not confer Linktree access, account authority, or permission to process visitor data. Return exact operator steps or an approval-gated handoff when a live action is not authorized.
Current Contract
- Linktree documents classic links and Link Apps as separate experiences created from the Links area.
- A classic link sends a visitor to the configured destination; an app can embed an experience on the profile.
- The public developer page invites registration for broader API and SDK access; it is not a public automation specification.
Authentication
For Admin work, use only the operator's individually provisioned Linktree account, documented Workspace role, and enabled MFA. Never request passwords, one-time codes, browser cookies, recovery codes, or session material. For partner automation, use only the authentication method, environment, scope, storage, rotation, and revocation process in the user-supplied approved partner contract. Public help pages do not establish a general API credential.
Instructions
- Confirm the authorized account, profile URL, approved destination, owner, rollback action, and test window.
- Inspect local campaign copy, destination inventory, and acceptance notes with Read, Glob, and Grep; do not search credential files.
- In Linktree Admin, add one classic link with an unambiguous title and the approved destination, leaving unrelated links unchanged.
- Open the public profile in a signed-out mobile viewport and desktop viewport; confirm title, placement, destination, HTTPS, and expected redirect chain.
- Exercise one safe failure path with a deliberately unpublished draft or a nonproduction destination, then confirm visitors cannot reach it.
- Use Write or Edit to record a redacted receipt containing timestamps, expected and actual destination hosts, and rollback status.
- Use WebFetch only to recheck the current official Linktree guidance when UI labels or feature availability differ.
Show full SKILL.md (166 more words)Show less
Approval Boundaries
Do not publish a campaign, collect visitor data, or change an established destination without the profile owner and campaign owner approving the exact change.
Output
Return profile, link title, destination host, viewport checks, redirect result, failure-path result, rollback state, evidence location, and go/no-go. Separate observed facts from assumptions.
Error Handling
| Condition | Response |
|---|---|
| Destination redirects unexpectedly | Pause publication and have the destination owner approve the complete redirect chain. |
| Link is visible before approval | Disable it immediately and record the exposure window. |
| Admin labels differ from the guide | Stop guessing and recheck current official help. |
Example
The example is a synthetic, redacted operator receipt, not proof of Linktree access or a live account change.
profile=/launch; item=Spring catalog; mobile=pass; desktop=pass; redirect=approved-host; failure-path=pass; rollback=ready; result=goResources
- Official documentation map — dated evidence and limits for this workflow.
Read the map before acting. Recheck current account and partner-specific evidence for plan-dependent or private behavior.
Next Steps
Revalidate source dates, owner approval, target profile, and rollback readiness before repeating the workflow in another account, Workspace, campaign, region, plan, or integration.
© 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/linktree-hello-world of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- references/official-docs.md
Open the folder on GitHubat commit cfae287
Compare with similar skills
Linktree Hello World 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 |
|---|---|---|---|---|---|---|
| Linktree Hello World this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Reproduce Chat Statesdifferent-ai/openwork | 24k | — | ~673 | Automated safety check: Pass | Custom licence | |
| Dynamo Jira TicketDynamoDS/Dynamo | 2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Moav E2EMotherofallVPNs/MoaV | 449 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Creating A Coral TaskHuman-Agent-Society/CORAL | 1.1k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Launch Rlmarin-community/marin | 3.9k | — | ~894 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Dynamo Jira Ticket
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
Moav E2E
MotherofallVPNs/MoaV
Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.
Creating A Coral Task
Human-Agent-Society/CORAL
Author a new CORAL task — the three pieces that must line up (task.yaml, seed/, a packaged grader/), the coral init → coral validate → smoke-test loop, and how to pick a grader pattern (stdout…
Launch Rl
marin-community/marin
Define, validate, submit, or restart a Marin SkyRL experiment through its artifact main.
Actionbook Web Test
actionbook/actionbook
Run browser-based web tests against websites using Actionbook CLI.
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
Categories
Questions about Linktree Hello World
What does Linktree Hello World do?
Run the smallest documented Linktree publish-and-verify workflow without inventing an API. Linktree Hello World is an agent skill from jeremylongshore/tons-of-skills-marketplace. Run the smallest documented Linktree publish-and-verify workflow without inventing an API.
When should I use Linktree Hello World?
Linktree Hello World fits situations like: launching a profile; proving a new Linktree setup; with smoke test Linktree.
How do I install Linktree Hello World in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill linktree-hello-world -a claude-code`. Or copy the skill folder (skills/.curated/linktree-hello-world in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/linktree-hello-world in your project. Claude Code loads it when a task matches its description.
How do I install Linktree Hello World in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill linktree-hello-world -a codex`. Or copy the skill folder (skills/.curated/linktree-hello-world in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/linktree-hello-world in your project. Codex loads it when a task matches its description.
Can I use Linktree Hello World 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 linktree-hello-world -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linktree-hello-world, .gemini/skills/linktree-hello-world, .github/skills/linktree-hello-world and .opencode/skills/linktree-hello-world in your project.
What does Linktree Hello World need to run?
SKILL.md names no scripts, command-line tools or credentials: Linktree Hello World 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; live work requires an authorized Linktree account and approval from the profile, Workspace, data, or partner-integration owner.
Does Linktree Hello World 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 Linktree Hello World 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 Linktree Hello World use?
Linktree Hello World 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 Linktree Hello World 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 384 tokens, read only when the agent opens those files.
What are the alternatives to Linktree Hello World?
Skills that share tags, products or a category with Linktree Hello World: Reproduce Chat States (different-ai/openwork, 24k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars), Moav E2E (MotherofallVPNs/MoaV, 449 stars) and Creating A Coral Task (Human-Agent-Society/CORAL, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Linktree Hello World?
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.