agentleFS
Sign inStart free
rylsherdamz-rgbrylsherdamz-rgb/stellar-forge/skills/data/SKILL.md

data

Skill17 starsChanged 2 months agoMITView on GitHub

Querying Stellar chain data via Stellar SDK (preferred), Stellar RPC, and Horizon (legacy). Covers SDK methods, JSON-RPC, REST endpoints, streaming, pagination, agentic kit integration.

16 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use content, frontend and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Rayan55050Skill

    content

    Создание контента: посты, статьи, тексты

    Also in 3 projects that use this

  • imehrSkill

    frontend

    Use when building UI components, pages, or features - guides Claude through the approved frontend stack (Next.js 15, React 19, Shadcn, Tailwind) with design-first workflow for complex UIs, enforcing patterns and quality standards

    Also in 4 projects that use this

  • ryu111Skill

    browser

    agent-browser CLI 瀏覽器自動化指南。E2E 測試、UI 調試、設計驗證。適用於需要實際操作瀏覽器的場景。

    Also in 3 projects that use this

  • alxyrginSkill

    writing

    Создание контента для личного бренда — статьи, посты, туториалы. Use when user asks to "напиши статью", "создай пост", "подготовь контент", "write article", "create content", or when task requires content creation for blogging, LinkedIn, Medium, or other publishing platforms.

    Also in 3 projects that use this

  • 0xSeroSkill

    security

    Also in 4 projects that use this

  • NVIDIASkill

    github

    Interact with GitHub using the gh CLI restricted to REST API only (no GraphQL). Use when the user wants to work with GitHub issues, pull requests, repos, releases, or Actions — especially in sandboxed environments where the GraphQL endpoint may be blocked. Trigger keywords - github, gh, pull request, PR, github issue, github actions, workflow, release, gh api.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All blockchain queries use useStellarData() (frontend) or Stellar SDK / RPC directly (backend).

    line 9
  2. Distinctive:

    Use the Stellar SDK directly:

    line 36
  3. Very specific:

    Read-only contract state: use useContract().read() (simulation, no tx)

    line 55

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Data — Stellar Chain Queries

All blockchain queries use useStellarData() (frontend) or Stellar SDK / RPC directly (backend). Never raw curl or manual RPC calls.

Source Files (published with this skill)

FileContents
templates/src/index.tsExpress server — balance endpoint, contract query endpoint, CORS
templates/src/services/stellar.tsRPC client — getBalances, queryContract, getContractData, getEvents, getTransaction

Agentic Kit (Frontend)

Import from @/hooks/use-stellar-data:

const { getBalances, queryContract, getContractData, getEvents, getTransaction, loading, error } = useStellarData();
MethodReturnsDescription
getBalances(address){asset, balance}[]All trustline balances + native XLM
queryContract(contractId, method, args[])ScVal | nullRead-only contract query (simulation)
getContractData(contractId, key)ScVal | nullRaw contract storage entry
getEvents(contractId, limit?)Event[]Contract events (newest first)
getTransaction(hash)TxResponse | nullCheck tx status + return value

Backend / API

Use the Stellar SDK directly:

import { rpc } from "@/lib/stellar-config";
const account = await rpc.getAccount(address);
const sim = await rpc.simulateTransaction(tx);
const sent = await rpc.sendTransaction(signedTx);
const events = await rpc.getEvents({ contractIds: [contractId] });

Raw RPC (if needed)

  • rpc.getLedgerEntries(keys) — raw ledger data
  • rpc.getNetwork() — network info
  • rpc.getLatestLedger() — current ledger seq
  • Horizon: GET /accounts/{id}, GET /claimable_balances, GET /payments

Strict Rules

  1. Frontend: always use useStellarData() — never raw RPC or curl
  2. Read-only contract state: use useContract().read() (simulation, no tx)
  3. State-changing contract calls: use useContract().write() (sign + submit)
  4. Backend: use rpc.* methods directly for server-side queries

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free