pier-cloud — Claude Code skill: Pier Cloud cost API, install guide
A skill for calling the Pier Cloud (Lighthouse) API: JWT auth, contexts, workspaces and FinOps view data through ready-made Python scripts.
Apache-2.0 ★ 141 updated 2026-10-29
npx skills add fabricioctelles/skills --skill pier-cloud -a claude-codeWhat pier-cloud does
The skill hands the agent the layout of Pier Cloud's Lighthouse API for cloud spend. It covers the JWT login at POST /auth, listing contexts, workspaces and workspace groups, and pulling FinOps view data with filters. Requests go to https://api.piercloud.io; a token is good for one hour, so long sessions need a refresh.
Scripts ship in scripts/: auth, workspaces with pagination, a single workspace or view, and view data. pier_cloud_client.py adds retries and token renewal. Endpoint details sit in references/REFERENCE.md, while references/TROUBLESHOOTING.md handles 401 and 404 responses.
Two things have to be in place first. Drop a .env into the skill folder holding PIERCLOUD_CLIENT_ID, PIERCLOUD_CLIENT_SECRET and PIERCLOUD_TENANCY_ID, then run pip install requests python-dotenv. Without that file the skill stops and tells you to get credentials from Pier Cloud. Mind the path too: workspace groups sit under /workspaces-groups.
What it helps with
- fetch a JWT and renew it before the hour runs out
- pull every workspace with automatic pagination
- read FinOps view data with filters applied
- look up a workspace group by id
- debug a 401 or 404 coming back from the API
Example prompts for the agent
- Log in to Pier Cloud and list the contexts I can see
- Pull all workspaces with the pagination script from the skill
- Get this workspace's view data, filtered by period
How to install pier-cloud
1Skills CLI (Vercel)
npx skills add fabricioctelles/skills --skill pier-cloud -a claude-code2Manually: put the files in place
~/.claude/skills/pier-cloud/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pier-cloud/
1Skills CLI (Vercel)
npx skills add fabricioctelles/skills --skill pier-cloud -a codex2Manually: put the files in place
.agents/skills/pier-cloud/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add fabricioctelles/skills --skill pier-cloud -a cursor2Manually: put the files in place
.cursor/skills/pier-cloud/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install fabricioctelles/skills skills/pier-cloud2Manually: put the files in place
.github/skills/pier-cloud/SKILL.md1Skills CLI (Vercel)
npx skills add fabricioctelles/skills --skill pier-cloud -a gemini-cli2Platform CLI
gemini skills install https://github.com/fabricioctelles/skills --path skills/pier-cloudManually: put the files in place
.devin/skills/pier-cloud/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about pier-cloud
How do I install pier-cloud in Claude Code?
Run npx skills add fabricioctelles/skills --skill pier-cloud -a claude-code. The skill then sits at ~/.claude/skills/pier-cloud/SKILL.md.
What does pier-cloud do?
It teaches the agent to call the Pier Cloud API: grab a token, list contexts, workspaces and workspace groups, and read FinOps view data. Ready-made scripts cover the common calls.
What does the skill need before it runs?
A .env file in the skill folder with PIERCLOUD_CLIENT_ID, PIERCLOUD_CLIENT_SECRET and PIERCLOUD_TENANCY_ID, plus the requests and python-dotenv packages. It will not continue without the .env.
Source text
SKILL.md · Apache-2.0
---
name: "pier-cloud"
description: "This skill should be used when the user needs to consume the Pier Cloud (Lighthouse) API for cloud cost management — including JWT authentication, listing contexts, workspaces, workspace groups, and FinOps data views. Trigger whenever there is a need to integrate, automate, or debug calls to the Pier Cloud platform via Python, Node.js, or cURL."
metadata:
author: ft.ia.br
version: "1.2"
date: 2026-09-21
repository: https://github.com/fabricioctelles/skills
license: Apache 2.0
keywords: ["pier", "piercloud", "lighthouse", "api", "finops", "cloud", "costs"]
category: library-and-api-reference
---
# Pier Cloud API
## Prerequisites
### Credentials
Locate the `.env` file in the skill directory with the following variables:
```env
PIERCLOUD_CLIENT_ID=your_client_id
PIERCLOUD_CLIENT_SECRET=your_client_secret
PIERCLOUD_TENANCY_ID=your_tenancy_id
```
If the `.env` file does not exist, inform the user that credentials must be obtained from the Pier Cloud platform before proceeding. Do not proceed without the `.env` file.
> Note: `PIERCLOUD_TENANCY_ID` is equivalent to the former `PIERCLOUD_BUSINESS_ID`. Scripts accept both as fallback.
### Python Dependencies
```bash
pip install requests python-dotenv
```
## Basic Configuration
The API uses JWT authentication. Required flow:
1. Authenticate via `POST /auth` with `client_id` and `client_secret` to obtain a JWT token
2. Include the token in all requests: `Authorization: Bearer {token}`
3. Renew the token upon expiration (default validity: 1 hour)
**Base URL**: `https://api.piercloud.io`
> Workspace groups live at `/lighthouse/tenancies/{tenancy_id}/workspaces-groups` (note the plural *workspaces*).
Verify the connection by running:
```bash
python scripts/pier-cloud-auth.py
```
## Available Scripts
Ready-to-use scripts in `scripts/`. See `scripts/README.md` for detailed instructions.
| Script | Description |
|--------|-------------|
| `pier-cloud-auth.py` | Authenticate and obtain JWT token |
| `pier-cloud-list-contexts.py` | List available contexts |
| `pier-cloud-list-workspaces.py` | List workspaces with pagination |
| `pier-cloud-get-workspace.py` | Get specific workspace details |
| `pier-cloud-get-all-workspaces.py` | Get all workspaces (automatic pagination) |
| `pier-cloud-list-views.py` | List views for a workspace |
| `pier-cloud-get-view.py` | Get specific view information |
| `pier-cloud-get-view-data.py` | Get view data with filters |
| `pier-cloud-list-workspace-groups.py` | List workspace groups (`/workspaces-groups`) |
| `pier-cloud-get-workspace-group.py` | Get workspace group by id |
| `pier_cloud_client.py` | Robust client with CLI and reusable library |
## Workflows
Follow the detailed workflows with request and response examples in `references/REFERENCE.md`:
- **Workflow 1** — Authentication and Token Retrieval
- **Workflow 2** — List Contexts
- **Workflow 3** — List Workspaces
- **Workflow 4** — Get Workspace Details
- **Workflow 5** — Get All Workspaces (Automatic Pagination)
- **Workflow 6** — Robust Client with Retry and Token Renewal
- **Workflow 9** — List Workspace Views
- **Workflow 10** — Get View Information
- **Workflow 11** — Get View Data with Filters
- **Workflow 12** — List Workspace Groups (`/workspaces-groups`)
- **Workflow 13** — Get Workspace Group Details
For endpoint reference, parameters, response structures, and cURL examples, see `references/REFERENCE.md`.
For error diagnosis (401, 403, 404, timeout, rate limiting), see `references/TROUBLESHOOTING.md`.
## Additional Resources
- **API Docs**: https://docs.piercloud.com/api-docs-pier-cloud
- **Public routes (EN)**: https://docs.piercloud.com/api-docs-pier-cloud/api-pier-cloud/public-routes-en-us
- **Pier Cloud Platform**: https://piercloud.com/en/
## Quality Checklist
- [ ] `.env` file present with `PIERCLOUD_CLIENT_ID`, `PIERCLOUD_CLIENT_SECRET`, and `PIERCLOUD_TENANCY_ID`
- [ ] Python dependencies installed (`requests`, `python-dotenv`)
- [ ] Authentication successful (JWT token obtained without errors)
- [ ] Correct endpoint being used (`/lighthouse/tenancies/{tenancy_id}/...`; groups → `workspaces-groups`)
- [ ] Token being renewed before expiration in long sessions
- [ ] Workspace/view IDs confirmed via listing before using directly
- [ ] Errors handled per `references/TROUBLESHOOTING.md`
© ft.ia.br · Apache-2.0 · fabricioctelles/skills