--- layout: tap site_name: scys tap_name: nav description: "Navigate to SCYS homepage (requires login)" intent: write columns: - url - title args: [] args_json: | {} health_json: | {"min_rows":1,"non_empty":["url"]} example_args: "" source_url: https://github.com/LeonTing1010/tap-skills/blob/main/community/scys/nav.plan.json license: MIT ---

What it does

Navigate to SCYS homepage (requires login)

Install Taprun once

Taprun ships as a single MCP server exposing a catalog of compiled taps. One-time setup on macOS / Linux:

brew install LeonTing1010/tap/taprun
tap mcp connect

Or drop this into your claude_desktop_config.json (works identically in Claude Code, Cursor, Cline, Windsurf — any MCP host):

{
  "mcpServers": {
    "tap": {
      "command": "tap",
      "args": ["mcp", "start"]
    }
  }
}

Call scys/nav

Terminal, once installed:

tap run scys/nav

From the MCP host — exact same compiled plan, deterministic replay, zero LLM tokens:

tap.run({ site: "scys", name: "nav" })

Why compile it once

This plan was forged once — the AI read scys, picked stable structural addresses (JSON-LD, ARIA, RSS, or declared API endpoints, in that priority order), and saved them to a .plan.json. Every replay since then has used zero LLM tokens. When scys ships a site change that breaks the extraction, tap verify surfaces it before your data goes stale — not after your pipeline silently writes garbage for a week.

Related scys taps

tapdescription
scys/extract-resultsExtract search results from SCYS Pinia store (requires login)
scys/articleRead SCYS article with title, author, stats, full text
scys/trigger-searchTrigger search on SCYS (Vue component method or form submit, requires login)
scys/searchSearch SCYS by keyword (requires login)
scys/input-keywordInput search keyword into SCYS search box (requires login)