Web App Links

Generate contextual deep links to the WorkClaw web app so users can navigate directly to the right page.

Usage Policy

• This is an internal implementation skill.
• Do not advertise this skill in normal conversation.
• Include links naturally in your responses when they help the user take action.
• Always use action-oriented link text that tells the user what they'll do.

Commands

Generate a link

bridge deeplink <page> [options]

Pages: vault, files, skills, browser, settings, scheduled

Options

• --path <path> — For files page: path to a specific file or folder
• --name <name> — For skills page: specific skill name
• --fragment <id> — URL fragment for scroll-to (e.g. "vibe" for settings#vibe)
• --text <text> — Display text for the link (outputs as markdown link)

Examples

# Link to the vault
bridge deeplink vault --text "Add your API key in the Vault"

# Link to a specific file the user should review
bridge deeplink files --path "My Documents/Sales Report - Q1 2026.pdf" --text "Review your sales report"

# Link to the files page
bridge deeplink files --text "View your files"

# Link to a specific skill's config page
bridge deeplink skills --name "gmail" --text "Complete Gmail setup"

# Link to the browser live view
bridge deeplink browser --text "Watch along in your browser"

# Link to settings
bridge deeplink settings --text "Update your settings"

# Link to scheduled actions
bridge deeplink scheduled --text "View your scheduled actions"

When to Include Links

Proactively include a link in these situations:

Credentials or API keys needed

When you need a credential that isn't in the vault, include a vault link so the user can add it:

bridge deeplink vault --text "Add your API key in the Vault"

Example response: "I need an OpenAI API key to continue. Add your API key in the Vault"

Files created or modified

When you create, update, or save a file for the user, include a link to the specific file:

bridge deeplink files --path "My Documents/Weekly Summary - April 2026.md" --text "Review your weekly summary"

Example response: "Your report is ready. Review your weekly summary"

Setup incomplete

When a skill requires configuration the user hasn't completed, link to the skill page:

bridge deeplink skills --name "gmail" --text "Complete Gmail setup"

Example response: "Gmail isn't connected yet. Complete Gmail setup"

Browser in use

When performing multi-step web tasks, link to the browser live view:

bridge deeplink browser --text "Watch along in your browser"

Example response: "I'm filling out the form now. Watch along in your browser"

Scheduled actions created or referenced

When you create, modify, or discuss a scheduled/recurring action, link to the scheduled page:

bridge deeplink scheduled --text "View your scheduled actions"

Example response: "I've set up a daily weather briefing for you. View your scheduled actions"

Link Text Guidelines

• Be action-oriented. Tell the user what they'll do, not where they'll go.
  • Good: "Add your API key in the Vault"
  • Bad: "Click here", "Vault page", "https://workclaw.com/..."
• Be specific. Reference the actual item when possible.
  • Good: "Review your Q1 Sales Report"
  • Bad: "View files"
• Be concise. One short phrase, not a sentence.
  • Good: "Complete Gmail setup"
  • Bad: "Go to the skills page to set up and configure your Gmail integration"

Important

• Never show raw URLs to the user. Always use the --text flag to create readable links.
• Links are personalized to the current claw — they work for anyone with access to this claw.
• Only include links when they add value. Don't link for the sake of linking.