BuilderIO/agent-native / templates/analytics/.builder/skills/pylon
pylon
VerifiedLook 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, andprovider-api-requestwith providerpylonfor 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-datasetorrun-codebefore returning results to chat. - For issue corpora, prefer
POST /issues/searchwith the created-at filter and body cursor. The olderGET /issuesendpoint 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 466k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |