← Back to Skills Marketplace
Sniplink
by
Jahfali-dev
· GitHub ↗
· v3.0.0
· MIT-0
147
Downloads
0
Stars
0
Active Installs
5
Versions
Install in OpenClaw
/install sniplink
Description
OpenClaw skill. One-shot URL saver for tools and services discovered on X, GitHub, or anywhere. Drop a link, get it categorized, tagged, and stored — no fric...
Usage Guidance
This skill generally does what it says (extracts and saves link metadata) but before installing ask the author/platform these questions: 1) Which runtime tools does it expect to exist (gh, curl, browser_navigate, web_fetch, web_search)? 2) Where are saved links stored (local agent storage, OpenClaw cloud, third‑party DB)? Who can read them and what is the retention policy? 3) The skill calls a third‑party fxtwitter API for tweets — are you comfortable that tweet text/URLs will be sent to that service? 4) Will it ever require GitHub or other credentials from you (GH_TOKEN, etc.)? If answers are unclear or you cannot verify the storage/third‑party endpoints, treat this as higher risk and avoid installing until clarified.
Capability Analysis
Type: OpenClaw Skill
Name: sniplink
Version: 3.0.0
The skill contains a hardcoded, highly specific absolute filesystem path in SKILL.md that includes a personal email address ([email protected]) for Obsidian storage. This indicates the skill is either tailored for a specific individual or contains uncleaned PII/configuration from a development environment, which is irregular for a distributed bundle. While it includes positive security patterns like mandatory user approval before data persistence, its reliance on an external third-party API (api.fxtwitter.com) and the specific path assumptions represent a privacy risk and potential functional instability.
Capability Tags
Capability Assessment
Purpose & Capability
The declared purpose (one-shot URL saver) matches the instructions: extracting metadata from GitHub, tweets, and web pages and presenting them for user approval. However the SKILL.md repeatedly instructs use of platform tools and CLIs (e.g., 'gh api', 'curl' to fxtwitter, 'web_fetch', 'browser_navigate', 'web_search') while the registry metadata lists no required binaries or credentials — a mild mismatch. It's plausible these are built-in agent tools, but the skill does not declare that dependency explicitly.
Instruction Scope
Instructions stay largely within the stated purpose and explicitly require user confirmation before saving. Positive boundaries are stated (do not scrape behind logins/paywalls, respect robots.txt). Two things to flag: (1) the skill directs network calls to a third-party proxy API (https://api.fxtwitter.com) which will receive tweet URLs/text — this is expected for tweet extraction but is a privacy/exfiltration surface the user should know about; (2) the instructions say 'save to database' but do not specify where that database lives or who can read it.
Install Mechanism
No install spec or code files — lowest technical risk. Nothing is downloaded or written by an installer step according to the registry data.
Credentials
The skill requests no env vars or credentials, which is consistent with the absence of declared secrets. But it references GitHub API usage via 'gh api' (which in practice can use GH tokens/config) and external HTTP calls; the SKILL.md does not explain whether it will rely on any existing agent credentials or require the user to supply GH/Twitter credentials. This ambiguity should be clarified.
Persistence & Privilege
always:false and user-invocable are appropriate. The main open question is persistence: the skill saves data to 'database' on user approval but does not say where (agent-local storage, cloud service owned by skill author, or user-owned storage). That gap affects who can access saved links and how long they're retained.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install sniplink - After installation, invoke the skill by name or use
/sniplink - Provide required inputs per the skill's parameter spec and get structured output
Version History
v3.0.0
Migrated storage from JSON to Obsidian vault. Each saved tool is now an Obsidian note with YAML frontmatter. Added master index with Dataview queries. SnipLink now integrates with Obsidian graph view, search, and wiki-links. Deleted old JSON database. Obsidian is now the single source of truth.
v2.8.1
Added fxtwitter.com API as primary tweet extraction method (no browser needed, no login, no CAPTCHA). Fallback chain: fxtwitter API -> browser -> ask user. Extracts tweet text, media, facets (embedded links) from JSON response.
v2.8.0
Added X/Twitter pipeline: tweet context understanding, smart link extraction from tweets, GitHub repo search by name. Added mandatory approval gate for all saves — user reviews extracted data before anything is stored. Fixed unreachable site handling (stop after 2 attempts).
v1.0.1
Updated description: OpenClaw skill, X/GitHub discovery use case, ADHD-focused
v1.0.0
New name, ADHD-focused description, GitHub API support for repo URLs, streamlined one-shot save workflow
Metadata
Frequently Asked Questions
What is Sniplink?
OpenClaw skill. One-shot URL saver for tools and services discovered on X, GitHub, or anywhere. Drop a link, get it categorized, tagged, and stored — no fric... It is an AI Agent Skill for Claude Code / OpenClaw, with 147 downloads so far.
How do I install Sniplink?
Run "/install sniplink" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Sniplink free?
Yes, Sniplink is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Sniplink support?
Sniplink is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Sniplink?
It is built and maintained by Jahfali-dev (@almohalhel1408); the current version is v3.0.0.
More Skills