Terminal
Terminal/Skill
Reference for how ngrok endpoints and Traffic Policy YAML rules work, with a catalog of all 26 actions.
By ngrok
Works with
npx skills add ngrok/skills --skill ngrok-engineTwo decisions sit behind almost every ngrok task:
This skill answers both at the level a job skill needs, and holds the detail in references/. Where to apply the result is a separate question - see ngrok-surfaces.
Make these decisions from the user's intent. Do not ask them to choose an endpoint type; they should not have to know the taxonomy.
forward-internal action. This is how a receiver stays off the public internet.The composed shape most jobs land on:
cloud endpoint (public, runs the policy) -> forward-internal -> internal endpoint -> local service
Protocol is a separate axis from type. HTTP is the default; TCP (SSH, RDP, databases) changes several things - a public TCP endpoint needs a reserved address, internal TCP URLs need an explicit port, the policy phase becomes on_tcp_connect, and the Kubernetes operator does not support TCP at all.
Full decision logic, bindings, and the TCP rules: references/endpoints.md.
Rules grouped by phase. Each rule has optional CEL expressions and a list of actions.
on_http_request:
- expressions:
- "req.url.path.startsWith('/admin')"
actions:
- type: deny
on_http_request, on_http_response, on_tcp_connect, on_event_stream_message.Grammar, CEL variables, Secrets and Vaults, the seven most-used actions, and how actions chain: references/traffic-policy.md.
All 26 actions, so you know what exists without fetching anything:
deny, forward-internal, http-request, log, restrict-ips, set-vars, terminate-tlsadd-headers, circuit-breaker, log, owasp-crs-request, rate-limit, redirect, remove-headers, request-body-find-replace, set-vars, url-rewriteadd-headers, compress-response, custom-response, log, owasp-crs-response, remove-headers, response-body-find-replace, set-vars, sse-find-replacebasic-auth, jwt-validation, oauth, openid-connect, owasp-crs-request, owasp-crs-response, restrict-ips, terminate-tls, verify-webhookcircuit-breaker, close-connection, deny, forward-internal, http-request, owasp-crs-request, owasp-crs-response, rate-limitNever guess an action's config. Look it up in two steps:
references/action-catalog.md - the index. One row per action: phases, whether it ends the chain, what it does.references/actions/<action>.md - that action's config fields, result variables, and an example.Read only the action file you need; the whole directory is ~12k tokens and one action is a few hundred.
references/traffic-policy.md are the ones existing job skills happen to use. They are not the interesting half - reach for the catalog whenever the task needs anything else.rate-limit returns its own 429, verify-webhook fails closed). Check the action's entry before adding a deny that duplicates it.policy.yaml so it survives the user adding a second surface later.