agentleFS
AI-ModConAI-ModCon/genesis-skills/skills/amsc-skills/amsc-data-movement-api/SKILL.md

amsc-data-movement-api

Skill30 starsChanged 50 days agoBSD-2-ClauseView on GitHub

Use the AmSC movement API at https://api.american-science-cloud.org/api/current to list transfers, submit tutorial transfers, inspect transfer status, and cancel completed or active transfers through the provided Python client.

  • Installs packages

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 0 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

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

    Use this skill when you need to work with the AmSC movement API at https://api.american-science-cloud.org/api/current.

    line 12
  2. Very specific:

    Use scripts/amsc_service_client.py as the default client.

    line 18
  3. Very specific:

    Treat references/endpoints.md as the source of truth for confirmed routes.

    line 19
  4. Very specific:

    Use references/examples.md for the known-good tutorial collection IDs and transfer payloads.

    line 20
  5. Very specific:

    Use examples/curl-examples.md when you need raw HTTP requests instead of the Python client.

    line 21
  6. Very specific:

    If the client prompts for interactive Globus login, copy the login URL into login.tmp so the user can complete auth and return the …

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

AmSC Data Movement API

Use this skill when you need to work with the AmSC movement API at https://api.american-science-cloud.org/api/current.

This skill is currently focused on the movement transfer surface. The confirmed API routes, working payloads, and tutorial collection examples are captured in the companion markdown files in this skill directory.

What the agent should do

  1. Use scripts/amsc_service_client.py as the default client.
  2. Treat references/endpoints.md as the source of truth for confirmed routes.
  3. Use references/examples.md for the known-good tutorial collection IDs and transfer payloads.
  4. Use examples/curl-examples.md when you need raw HTTP requests instead of the Python client.
  5. If the client prompts for interactive Globus login, copy the login URL into login.tmp so the user can complete auth and return the authorization code.

Current configuration

Base URL: https://api.american-science-cloud.org/api/current
Resource server: 35bf38d3-4b30-42c8-ac9f-e39cec6516bf
Primary scope: https://auth.globus.org/scopes/35bf38d3-4b30-42c8-ac9f-e39cec6516bf/amsc
Client script: .claude/skills/amsc-data-movement-api/scripts/amsc_service_client.py
Token cache: .claude/skills/amsc-data-movement-api/scripts/tokens.json (written next to the client script — live credentials, never commit)

Confirmed commands

The client currently supports these five commands:

  1. --transfers
  2. --start-transfer '<TransferInputs JSON>'
  3. --start-globus-transfer '<GlobusTransferInputs JSON>'
  4. --get-globus-transfer TRANSFER_ID
  5. --delete-globus-transfer TRANSFER_ID

Known working tutorial flow

The following tutorial collections are confirmed in this repo:

  • Source: 6c54cade-bde5-45c1-bdea-f4bd71dba2cc
  • Destination: 31ce9ba0-176d-45a5-add3-f37d233ba47d
  • Source path: /home/share/godata/
  • Destination path: ~/

Both of these transfer creation paths have succeeded in live testing:

  • POST /movement/transfer
  • POST /movement/transfer/globus

The direct Globus route may temporarily return 409 if an identical transfer is already in progress. Retrying after the earlier transfer completes is sufficient.

Files in this skill

  • references/authentication.md - login flow, token cache, and consent behavior
  • references/endpoints.md - confirmed transfer routes and payload shapes
  • references/examples.md - tutorial collection IDs and ready-to-run examples
  • examples/curl-examples.md - raw curl examples for all confirmed routes
  • scripts/amsc_service_client.py - Python client for the AmSC API

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.