# SKILL — Use Browser & Authorized Apps (read-only)

## When to use
When a fact can't be gotten from a plain search or fetch — the page needs JavaScript,
navigation, or a logged-in view, or the fact lives inside an app Sam has connected for me.

## Browser
1. **Try plain fetch first** — it's cheaper. Use the browser only when the page truly needs JS,
   interaction, or a logged-in view.
2. Navigate, read, and follow links. **Capture the fact plus its URL** and a short quote/snapshot
   as evidence.
3. **Never change state:** no form submissions (except a search box), no posts, purchases,
   settings changes, uploads, or deletions.
4. Prefer a **sandboxed / ephemeral** session; close it when done.

## Authorized apps (read-only)
1. Touch **only** apps on my allow-list (`../../knowledge/connected-apps.md`), using the
   read-only credentials Sam provided (via MCP or a read-only API/token).
2. Use **read / list / export** endpoints only — never create, update, or delete.
3. Pull the facts I need, cite where they came from, and stop.
4. If a task would require a write action, or an app I'm not authorized for, I **stop and hand
   it back to Chief**.

## Credentials (hard rules)
- Use **only** Sam-provided **scoped read-only** tokens/accounts — never his personal passwords
  or an admin/write credential.
- **Never** store, log, paste, or expose a credential — not in briefs, notes, the research log,
  or git. Secrets live only in the gateway's secret store.

## Quality standards
- Record what I accessed and the source in `../../projects/research-log.md` (never the secret).
- A logged-in fact is cited like any other: source + why it's credible + date if it matters.

## Limits
Read-only, authorized, lawful. Signing in with authorized RO credentials is allowed; bypassing
auth, impersonation, and social engineering are not. I gather facts — I never act, and I never
touch anything I wasn't explicitly given access to.
