connect-device
Skill131 starsChanged 4 months agoMITView on GitHub
Connect the owner's own computer (Mac, Linux or Windows) or Chrome browser to Ship with a pairing invitation, give them the exact commands or extension steps, and confirm the connection.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- browser-targetSkill
- contactsSkill
- event-sourcesSkill
- gsv-manualSkill
- image-readingSkill
- memorySkill
- process-orchestrationSkill
- skill-authoringSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Run targets through Shell on target gsv.
- Very specific: line 14
Check targets list --json first.
- Very specific: line 17
When the work needs a computer or browser but not the owner's own, a cloud instance may do: see instance catalog.
- Very specific: line 19
Ask for the device's name, as it should appear (for example "work laptop"), and its platform: mac, linux, windows or browser.
- Very specific: line 40
Ask the owner to say when they are done, then check targets list --online for the new target and report what you see, not what should …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Connect a Device
Run targets through Shell on target gsv. Use targets --help for syntax.
The owner can also connect one themselves: in Work, connect beside
Connections opens the same invitation with copy buttons.
Before Pairing
- Check
targets list --jsonfirst. The device may already be connected, or offline and due to reconnect on its own. To pair an existing target again, pass--id TARGET --replace. - When the work needs a computer or browser but not the owner's own, a cloud
instance may do: see
instance catalog. - Ask for the device's name, as it should appear (for example "work laptop"),
and its platform:
mac,linux,windowsorbrowser.
Create the Invitation
targets pair --name NAME --platform PLATFORM returns JSON with an invitation
that lasts ten minutes. Share it only with the owner, in this conversation.
For a computer, the result has installCommand and pairCommand. Tell the
owner to open PowerShell on Windows (works best if opened with Administrator privileges), or Terminal otherwise, then give each
command in its own fenced code block, powershell on Windows and sh
otherwise, exactly as returned: never inline, shortened or reworded, so it
copies cleanly. The first installs the gsv app; the second connects the
computer.
For a browser, the result has extensionUrl, code and instructions. Give
the download link, the steps from instructions in plain words, and the code
in its own fenced block.
Confirm
Ask the owner to say when they are done, then check targets list --online
for the new target and report what you see, not what should happen. If the
invitation expired or was lost, targets pair list shows the open ones; cancel
the stale one with targets pair cancel ID and create another.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

