nvidia-api-catalog
Skill2 starsChanged 19 days agoLicence not identifiedView on GitHub
Find a live model on NVIDIA's hosted API catalogue (build.nvidia.com) and call it. Lists model ids and checks one id with keyless GET requests to integrate.api.nvidia.com, including retired models and their end-of-life dates. Documents the chat completion call with a key read from NVIDIA_API_KEY. NVIDIA's free developer access is for prototyping and testing only. Use when asked which models NVIDIA hosts, whether a model id still works, or how to call one.
- Reads credentials
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- llms-full.txtllms.txt
- llms.txtllms.txt
- abn-lookupSkill
- api-skillSkill
- asic-registersSkill
- au-business-checkSkill
- company-checkSkill
- creator-audienceSkill
- nz-companies-officeSkill
- uk-companies-houseSkill
- us-sec-edgarSkill
- vet-before-installSkill
- youtube-channel-profileSkill
- youtube-creator-researchSkill
- youtube-video-themesSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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
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.