agentleFS
Sign inStart free
stackqlstackql/stackql-skills/skills/pull-provider/SKILL.md

pull-provider

Skill0 starsChanged 8 months agoMITView on GitHub

Pull one or more StackQL providers from the registry. Supports version pinning with name@version syntax. Lists available providers when called with --list.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    If not found, delegate to /stackql-skills:install-stackql and then continue.

    line 19
  2. Very specific:

    If --list is in $@, list all available providers:

    line 23
  3. Distinctive:

    Run each pull command:

    line 46
  4. Distinctive:

    After pulling, verify the providers are available:

    line 60

≈ “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

Arguments: $@

Step 1 - Check StackQL is installed

command -v stackql

If not found, delegate to /stackql-skills:install-stackql and then continue.

Step 2 - Handle --list flag

If --list is in $@, list all available providers:

stackql exec "REGISTRY LIST;" --output json

Present the results as a table showing provider name and version, then stop.

Step 3 - Show currently installed providers

stackql exec "SHOW PROVIDERS;" --output json

Note which providers are already installed so you can report additions vs updates.

Step 4 - Pull each provider

For each argument in $@:

  • name -> REGISTRY PULL name;
  • name@version -> REGISTRY PULL name v<version>;

Run each pull command:

stackql exec "REGISTRY PULL <provider>;"

Or with a version:

stackql exec "REGISTRY PULL <provider> v<version>;"

Step 5 - Verify

After pulling, verify the providers are available:

stackql exec "SHOW PROVIDERS;" --output json

Step 6 - Report

For each provider pulled, report success or failure. If successful, suggest next steps:

Provider <name> is ready. Next steps:

  • Set up auth: /stackql-skills:auth-setup <name>
  • Explore services: /stackql-skills:explore <name>
  • Run a query: /stackql-skills:query "SELECT ... FROM <name>.<service>.<resource> WHERE ..."

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