Manage Linode cloud infrastructure programmatically via its REST API.
npx skills add https://github.com/rawveg/skillsforge-marketplace --skill linode-api
Please help me install this Agent Skill. Skill: linode-api Source: https://github.com/rawveg/skillsforge-marketplace/tree/main/linode-api Command: npx skills add https://github.com/rawveg/skillsforge-marketplace --skill linode-api
This Skill provides guidance for interacting with Linode's REST API to manage compute, networking, storage, and billing.
Create a Linode instance via the REST API and fetch account information.
High-intent search queries and answers about installing and using this skill.
Linode REST API authentication uses personal access tokens (PATs) with Bearer token headers. Generate a token in your Linode account settings and include it in API requests as `Authorization: Bearer [token]`. This method supports programmatic access to all cloud infrastructure resources without sharing account credentials.
Yes, Linode's REST API supports full management of compute instances, domains, DNS records, volumes, and NodeBalancers. You can create, update, delete, and query resources across all infrastructure categories via authenticated REST endpoints, enabling complete Infrastructure-as-Code workflows.
Linode REST API uses envelope-based pagination with `X-Total-Count` headers and `page` and `page_size` query parameters. Results are returned in batches; iterate through pages by incrementing the page parameter until all results are retrieved, reducing API load for large datasets.
Linode maintains v4 as the stable REST API version with comprehensive resource coverage and v4beta for early-access features. Both versions use the same authentication and pagination mechanisms; v4beta endpoints may change before promotion to stable.
Linode REST API supports advanced filtering via query parameters to narrow results by resource attributes. Combined with pagination, filtering enables efficient retrieval of specific instances, domains, or other resources without fetching entire resource lists.
While Linode REST API calls work with standard HTTP clients and curl, official client libraries simplify authentication, pagination, and error handling. Direct REST calls are fully supported; libraries are optional but reduce boilerplate for complex workflows.
evolv3aiProvision Linode virtual machines, firewalls, and Kubernetes clusters.
rajyeole6Monitor infrastructure and manage cloud resources with Terraform and Prometheus.
JonathanMitchell1234Monitor network elements, process billing data, and configure 5G network slices.
jholhewresManage cloud infrastructure as code with Terraform CLI.
