go

Execute saved shortcuts to open files, URLs, or bookmarks by name.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/rupertsworld/skills --skill go-rupertsworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: go
Source: https://github.com/rupertsworld/skills/tree/main/go
Command: npx skills add https://github.com/rupertsworld/skills --skill go-rupertsworld

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Access frequently used files, URLs, and bookmarks with a single shortcut, reducing time spent navigating your workspace.

Core Features & Use Cases

  • Direct access to files, URLs, or .webloc bookmarks via a named shortcut.
  • Automatic resolution and execution of the matched resource, with a fallback to show available shortcuts.
  • Persistence of resolved shortcuts to speed future sessions.

Quick Start

Ask the agent to go to a saved shortcut by name to open the associated resource.

Frequently Asked Questions about go

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create shortcuts to open frequently used files and URLs by name?

To launch shortcuts by name, you define a keyed collection of file paths, URLs, or .webloc bookmarks. The tool matches your requested name to this collection and executes the associated resource directly.

Can I use named bookmarks to automate navigation to local files and web links?

Named bookmarks automate navigation by resolving a saved shortcut to its target file, URL, or .webloc resource. When you ask the agent to go to a specific name, it opens the matched link without manual searching.

What happens if a named shortcut does not exist when I try to open a file or URL?

When a named shortcut does not exist, the system applies a fallback mechanism that shows available saved shortcuts. This ensures you can verify existing names and correct any mismatched navigation requests.

Do I need a persistence mechanism to store resolved shortcuts for future sessions?

A persistence mechanism is required to store resolved file and URL targets for future sessions. This saves the matched shortcut data locally, speeding up subsequent navigation by avoiding repeated manual lookups.

What's the best way to organize a keyed collection of shortcuts for daily workspace navigation?

Organizing a keyed collection requires mapping unique names to your desired file paths, URLs, and bookmarks. This structure allows the launcher to quickly find and execute the correct resource when you request it by name.