AGENT SKILL

instafy-skill-router

Decide which Instafy skill(s) to apply for a user request (browsing vs previews vs secrets, etc).

License 许可
AGPL-3.0
最近更新
2026-11-15
Stars
★ 0
Forks
1

01 前言 Front Matter

name
instafy-skill-router
description
Decide which Instafy skill(s) to apply for a user request (browsing vs previews vs secrets, etc).
context_kind
meta
max_children
3
always_include
true
context_parent
instafy-persistent-contexts
context_children
instafy-automations, instafy-browser-automation, instafy-byoc-ai-credentials, instafy-collaboration, instafy-conversation-history, instafy-diagnostics, instafy-frontend-previews, instafy-git-canonical-conflicts, instafy-git-canonical-sync, instafy-integration-onboarding, instafy-interactive-artifacts, instafy-learning-policy, instafy-location-sharing, instafy-research-team, instafy-runtime-flavors, instafy-secrets, instafy-skill-import-compat, instafy-space-review, instafy-web-research

03 SKILL.md 正文

Skill router (meta)

Never prune: yes

Goal: keep behavior consistent by selecting the right skill(s) based on the user’s request.

Treat the selected skill set as the active branch of the persistent context tree for this turn.

How to use (strict)

  1. Skim the Skills index in the project memory snapshot (names + descriptions).
  2. Pick the smallest set of skills that apply.
  3. Follow those skill runbooks. Do not invent new workflows when a relevant skill exists.

Notes:

  • Do not mention “skills” to the user unless they asked.
  • Prefer skill guidance over ad-hoc shell commands.
  • If two skills apply, you may combine them, but keep the execution mode clear (for example: “Tunnel preview mode” vs “Live browser assist mode”).
  • An outside lookup that is unavailable (exit 4, status: "unavailable": a place search, a router, a store's site did not answer) is not "not found": never retry it with another query or call the thing missing. Use what was found, say plainly what could not be looked up, and offer to try again.

Routing rules (default)

Use these mappings unless a project-specific skill overrides them.

  • A site or server running in this space (a dev server, a static file server, "show me a preview", localhost, 127.0.0.1, any port here)

    • Use instafy-frontend-previews: show it to people with a private Studio preview card (instafy preview open ... --serve-cmd "<command>" --start, which also keeps it running after the turn) and check it yourself with instafy preview check.
    • Not Instafy's browser: its safety policy blocks this space's own addresses (localhost, 127.0.0.1, 0.0.0.0, private addresses) and non-web ports.
  • Anything a public web page would help with (look something up, check or verify a public page, show a site's screens, guided clicks, sign-in)

    • Use instafy-browser-automation and open the browser without asking in chat first; its site and action prompts still apply. Not for a site running in this space (above).
    • Use the exposed Personal or Shared Browser tools. If neither is exposed, follow the skill's request_browser handoff so Studio can open or resume the appropriate browser.
  • A fact from the web for an answer or a page (prices, opening hours, timetables, addresses, places or products to compare, "with sources")

    • Use instafy-web-research: which sources to read, how many, cross-checking, citing, and the link-only sites.
    • Read public pages that need no JavaScript or sign-in with instafy web read <url…> --json (no browser card); its provenance is what to cite.
    • Combine with instafy-browser-automation when the reads go through Instafy's browser (a page instafy web read reports as needs_browser, an aggregator, a page the person wants to see); one card may carry up to 6 related reads.
  • Public page text / element counts / computed CSS / screenshot verification

    • Use instafy-browser-automation.
    • Prefer instafy_local_browser.observe when it is exposed; it is headless and read-only, not an interactive or authenticated session.
  • A page to tap through: map, ranking, comparison or shopping table, dashboard, quiz, timeline, planner, tracker

    • Use instafy-interactive-artifacts: it picks the builder from the installed skills (a skill for that kind of page, such as a map, instafy-bound-sites for values checked per click, a starter site otherwise) and shows the result with instafy preview open.
    • Many items to research live first (a long trip, several products): instafy-research-team.
  • Near me / around me / my current location (the user's own position; no place named)

    • Use instafy-location-sharing.
    • A named city, area, address or venue is not a location request: use it as given.
    • Prefer an inline location action card over telling the user to search manually.
    • Combine with instafy-browser-automation when a page would help after location is shared.
  • Shareable preview URL / mobile-friendly link / “can you show me a demo link”

    • Use instafy-frontend-previews (tunnel preview mode).
    • Ask for consent before creating a public URL. Check the site yourself with instafy preview check; Instafy's browser can open only its public tunnel URL, never the space's own address.
  • Missing env vars / API keys / OAuth client setup / dashboards

    • Use instafy-integration-onboarding for the step-by-step plan.
    • Use instafy-secrets to request/store secrets (never write secrets to files).
    • When a provider's screens are involved, combine with instafy-browser-automation and open the browser to show them the way.
  • Git canonical syncing / conflicts

    • Use instafy-git-canonical-sync for normal sync.
    • Use instafy-git-canonical-conflicts when sync hits conflicts.
  • Runtime flavor/image selection

    • Use instafy-runtime-flavors.
  • Bring-your-own AI credentials

    • Use instafy-byoc-ai-credentials.
  • Invite teammate / add collaborator / share this space by email / change teammate access

    • Use instafy-collaboration.
    • Direct the user to the interactive Invite UI or the Studio composer /invite <email> <viewer|builder> command.
    • For existing-member or pending-invite changes, direct the user to Invite → Manage access.
    • Interpret “write access” as builder; project sharing only offers viewer and builder.
    • Do not run CLI sharing commands from a runtime job. Scoped runtime/tool tokens intentionally cannot manage sharing.
  • Earlier chat / other conversation / previous discussion / “we talked about this before”

    • Use instafy-conversation-history.
    • Prefer normal-language lookup over teaching special composer syntax.
    • Search first with instafy conversation search "<keywords>", then inspect with instafy conversation show <id> --transcript.
  • Getting started / “I'm new here; what should I work on first?”

    • When no goal is stated and the person is not asking to inspect existing work, ask one short question about what they want to build or solve in this chat. Do not require a history review just to ask it, or claim the space is empty without evidence.
    • If they already gave a goal, help with that goal directly.
  • Review this space / useful next actions from existing work / “what should we pick up next?”

    • Use instafy-space-review for a bounded, on-demand review in the current chat.
    • Read prior recommendations and accessible conversation evidence before proposing at most one useful next step. Respect delivered, accepted, dismissed and postponed topics; do not schedule reviews or execute the suggestion.
  • Start recurring space reviews / schedule check-ins / start check-ins and review now

    • Use instafy-automations to list and create or update the space_review schedule. For an explicit immediate review too, trigger that schedule once after saving it; do not also review in the setup chat.
  • Failed run / runtime error / diagnose / investigate / support report

    • Use instafy-diagnostics.
    • Read signed-in-user diagnostics first; never scrape local logs or use raw/operator APIs.
    • Keep diagnosis read-only unless the user explicitly asks to file a report, then preview and obtain confirmation before submitting once.
  • “Don't remind me again” / “remind me tonight” / “let's do this weekend” / “check in less often” / reminders / schedules / recurring tasks / automation management

    • Use instafy-automations.
    • For feedback on this chat's proactive suggestion, use instafy recommendations current, then dismiss or remind. Save the preference before acknowledging it.
    • Changes to overall check-in frequency belong on the existing space review automation. Ordinary reminders use the normal automation commands.
    • Interpret times in the user's known local timezone unless they explicitly say otherwise; ask when it is missing. A postponement schedules a reminder, not automatic execution of the task.

Ambiguous cases

  • If the person asks to "open it in the browser" for a site running in this space: say in one line that the browser's safety policy blocks the space's own addresses, point to the preview card (open one with instafy-frontend-previews if there is none), and offer a public link only after they agree to one.
  • If the user asks “use a browser” but they actually want a shareable link:
    • Ask one short clarification: “Do you want a shareable public preview link, or a live browser walkthrough here?”
  • For current information (news, prices, releases, status pages):
    • Read it with instafy web read or instafy-browser-automation, choosing and citing sources with instafy-web-research.
    • Answer from memory only when no page can be read, and then say no live browsing was used.

04 同仓库更多 Skills