# lottiefiles-library-account

Searches, inspects, and edits LottieFiles library and account resources through GraphQL, within the connected account's permissions.

Skill by LottieFiles. Category: Data and backend.

## Install

Project (for this project only):

```sh
npx skills add lottiefiles/creator-agent-plugin --skill lottiefiles-library-account
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

Global (for every project on this machine):

```sh
npx skills add lottiefiles/creator-agent-plugin --skill lottiefiles-library-account -g
```

Works with: Claude Code, Codex CLI, Cursor, Antigravity, Copilot CLI, opencode.

## Tags

- Runs on your computer: It runs as a program on your machine, with your access.

## Security audits

- Gen Agent Trust Hub: Pass
- Socket: Pass
- Snyk: Pass

Installs: 1. Installs counted by skills.sh. [Open on skills.sh](https://www.skills.sh/lottiefiles/creator-agent-plugin/lottiefiles-library-account)

## Source

[Open the source](https://github.com/lottiefiles/creator-agent-plugin/tree/HEAD/content/skills/lottiefiles-library). Checked 2026-10-10. This summary may contain AI-generated text, so it can be wrong. Check the source before you rely on it.

## SKILL.md

````markdown
---
name: lottiefiles-library-account
description: Search or inspect LottieFiles library or account data with lf_graphql. Use when the user asks to find, list, inspect, upload, update, delete, or organize LottieFiles resources.
---

# LottieFiles library and account workflows

Full LottieFiles GraphQL access is intentional. It supports the capabilities that the connected account has. It does not grant extra scopes. Read [the contract reference](../../references/tool-contract.md) before a tool call.

1. Discover the needed schema and capability first. Use only fields that the current public schema confirms.
2. Read before a change. Inspect the target resource and its ownership or current state.
3. Request the minimum fields. Send values as variables. Do not put secrets in a query.
4. Paginate lists. Use the returned cursor and a user-approved limit.
5. Before a mutation or delete, state the target and effect. Require explicit user intent and host confirmation.
6. Inspect the response after a mutation. Handle GraphQL partial errors and report which data is reliable.

Never bypass scopes. Never log tokens or query variables. Do not infer a field or mutation name from a human label.
````

- Previous: [lottiefiles-animation-workflows](https://syn4pse.dev/terminal/lottiefiles-animation-workflows.md)
- Next: [profiling-transaction-fingerprints](https://syn4pse.dev/terminal/cockroachdb-profiling-transaction-fingerprints.md)
- [Terminal](https://syn4pse.dev/terminal.md)
- [Suggest a change](mailto:terminal@syn4pse.dev?subject=Terminal%20suggestion)
