Atlas / Skills / builderio / Pylon

PylonCAUTION

skills/builderio/pylon

Agent skill by builderio · agent native · agents · ai · Audited 2026-10-14

⚑ Report / re-scan Source ↗

A framework for building agentic apps

Verdict

CAUTION

Grade

Trust score

89 /100

Version

—

Hosts

1 documented

License

—

Stars

7,191

Overview

A framework for building agentic apps

Read from source at commit d31edd75948aOBSERVED · 2026-10-14

Host compatibility

What the documentation claims. We have not run a compatibility test.

Host	Status	Notes
cursor	mentioned

What it tells the agent

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: pylon
description: >
Look up customer support tickets and account history via Pylon.
Use this skill when the user asks about support tickets, customer issues, or support history.
---

# Pylon Integration (Support)

Pylon access uses the shared provider API runtime. Do not add a separate Pylon
client. `/api/pylon/issues` remains only as a thin compatibility route for an
existing dashboard and delegates to the same action/provider runtime.

## Access Paths

- Use `provider-api-catalog`, `provider-api-docs`, and
`provider-api-request` with provider `pylon` for bounded account, contact,
and issue queries.
- Use a data program with `providerFetchAll("pylon", ...)` for reusable joins,
exhaustive support-ticket analysis, or dashboard sources. Existing risk
meeting programs demonstrate the HubSpot-to-Pylon domain join.
- Stage large responses and reduce them with `query-staged-dataset` or
`run-code` before returning results to chat.
- For issue corpora, prefer `POST /issues/search` with the created-at filter and
body cursor. The older `GET /issues` endpoint has a 30-day window and should
not be used for broad dashboard coverage.

Authentication is resolved from the current viewer's scoped Pylon credential
through the shared provider runtime.

## Key Patterns & Gotchas

- Confirm the current endpoint, time-window, filter, and cursor contract with
`provider-api-docs`; do not impose a fixed lookback window in a wrapper.
- Report inspected issue/account counts, pagination coverage, failed pages, and
truncation. A sampled response cannot support an exhaustive absence claim.
- Query Pylon directly unless the user explicitly asks for a warehouse copy.

Trust audit

CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.

Layer	What it checks	Result
L0	Provenance & inventory	WARN
L1	Static analysis of the code	NA
L2	Instruction surface (what it tells the agent)	PASS
L3	Class-specific surface	PASS
L4	Behavioural (sandbox)	SKIPPED

What the source does

Filesystem: none-observed
Network: none-observed
Shell: none-observed
Dependencies: pinned
Secrets in source: none-found