file-ops
Browse, read, and write files on the remote host machine.
Free to get · One-click to use
Browse, read, and write files on the remote host machine.
Find the best local LLM for your machine. Tests speed, quality and RAM fit, then tells you if a model is worth running on your hardware.
dsub job submission and monitoring for All of Us Researcher Workbench on Google Cloud. Use when: (1) submitting distributed computing jobs via dsub, (2) checking job status with dstat, (3) choosing machine types or disk configurations for cloud jobs, (4) debugging dsub failures or provider issues. Encodes provider quirks, machine type constraints, and the dsub_script()/check_dsub_status() patterns.
Communicate with the local stateful agent system via the GitHub relay. Use this skill when the user wants to interact with their local machine remotely — reading memory files, running shell commands, or delegating tasks to the local Claude Desktop agent. Triggers include phrases like: "on my local machine", "check my local files", "run this on my home computer", "ask my local Claude", "read my memory files", "what's in my core memory", "what's on my home machine", "run this locally". Requires the github skill for relay transport scripts. --- # AI Messaging Skill This skill enables Claude.ai (web or mobile) to communicate with the local stateful agent system running on Fran's home machine. It uses the GitHub relay transport protocol (provided by the github skill) to send signed requests to the local MCP bridge and receive signed responses. ## Prerequisites - The **github skill** must be installed (provides `relay_send.py`, `relay_receive.py`, and `relay_common.py` in its `scripts/` directory). - Environment variables `GITHUB_TOKEN` and `RELAY_HMAC_SECRET` must be set (available via personal instructions). - The relay repository is `fpl9000/claude-relay`. ## When to Use This Skill Use this skill when the user wants to do something that requires their local machine — a Windows 11 system running the MCP bridge server. Common triggers: - "Read my core memory" / "What's in my memory files?" - "Run this on my local machine" / "Check something on my home computer" - "Ask my local Claude to..." / "Have Claude Desktop do..." - "What's the status of [project] locally?" - "Run `git status` on my mcp-bridge repo" - Any reference to the local machine, local files, or the stateful agent system Do NOT use this skill for operations that can be performed directly from Claude.ai (e.g., reading GitHub repos via the github skill's existing scripts, web searches, or general knowledge questions). ## Operations The relay supports three operations. Choose the simplest one that can accomplis
skill-sample/ ├─ SKILL.md ⭐ Required: skill entry doc (purpose / usage / examples / deps) ├─ manifest.sample.json ⭐ Recommended: machine-readable metadata (index / validation / autofill) ├─ LICENSE.sample ⭐ Recommended: license & scope (open source / restriction / commercial) ├─ scripts/ │ └─ example-run.py ✅ Runnable example script for quick verification ├─ assets/ │ ├─ example-formatting-guide.md 🧩 Output conventions: layout / structure / style │ └─ example-template.tex 🧩 Templates: quickly generate standardized output └─ references/ 🧩 Knowledge base: methods / guides / best practices ├─ example-ref-structure.md 🧩 Structure reference ├─ example-ref-analysis.md 🧩 Analysis reference └─ example-ref-visuals.md 🧩 Visual reference
More Agent Skills specs Anthropic docs: https://agentskills.io/home
├─ ⭐ Required: YAML Frontmatter (must be at top) │ ├─ ⭐ name : unique skill name, follow naming convention │ └─ ⭐ description : include trigger keywords for matching │ ├─ ✅ Optional: Frontmatter extension fields │ ├─ ✅ license : license identifier │ ├─ ✅ compatibility : runtime constraints when needed │ ├─ ✅ metadata : key-value fields (author/version/source_url...) │ └─ 🧩 allowed-tools : tool whitelist (experimental) │ └─ ✅ Recommended: Markdown body (progressive disclosure) ├─ ✅ Overview / Purpose ├─ ✅ When to use ├─ ✅ Step-by-step ├─ ✅ Inputs / Outputs ├─ ✅ Examples ├─ 🧩 Files & References ├─ 🧩 Edge cases ├─ 🧩 Troubleshooting └─ 🧩 Safety notes
Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.
We provide keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.
Quick Start:
Import/download skills (.zip/.skill), then place locally:
~/.claude/skills/ (Claude Code)
~/.codex/skills/ (Codex CLI)
One SKILL.md can be reused across tools.
Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.
A skill is a reusable capability package, usually including SKILL.md (purpose/IO/how-to) and optional scripts/templates/examples.
Think of it as a plugin playbook + resource bundle for AI assistants/toolchains.
Skills use progressive disclosure: load brief metadata first, load full docs only when needed, then execute by guidance.
This keeps agents lightweight while preserving enough context for complex tasks.
Use these three together:
Note: file size for all methods should be within 10MB.
Typical paths (may vary by local setup):
One SKILL.md can usually be reused across tools.
Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.
Example: retrieval + writing + automation scripts as one workflow.
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
Most common reasons:
We try to avoid that. Use ranking + comments to surface better skills: