linkai-agent
Skill260 starsChanged 8 months agoApache-2.0View on GitHub
Call LinkAI applications and workflows. Use bash with curl to invoke the chat completions API.
- Reads credentials
- Sends data out
In this repository2 other files it gives its agents.
- skill-creatorSkill
- web-fetchSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Call LinkAI applications and workflows through the chat completions API.
- Very specific: line 27
Add your apps/workflows in config.json.
- Distinctive: line 31
Use the bash tool with curl to call the API.
- Very specific: line 46
Add --max-time 120 to curl for long-running tasks (video/image generation)
- Very specific: line 48
On Windows cmd: Use %LINKAI_API_KEY% instead of $LINKAI_API_KEY.
≈ “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.
Files
LinkAI Agent
Call LinkAI applications and workflows through the chat completions API. Available apps are loaded from config.json.
Setup
This skill requires a LinkAI API key.
- Get your API key from LinkAI Console
- Set the environment variable:
export LINKAI_API_KEY=Link_xxxxxxxxxxxx(or use env_config tool)
Configuration
- Copy
config.json.templatetoconfig.json - Add your apps/workflows in config.json. The skill description is auto-generated from this config when loaded.
Usage
Use the bash tool with curl to call the API. Prefer curl to avoid encoding issues on Windows PowerShell.
curl -X POST "https://api.link-ai.tech/v1/chat/completions" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $LINKAI_API_KEY" \
-d '{
"app_code": "<app_code>",
"messages": [{"role": "user", "content": "<question>"}],
"stream": false
}'Optional parameters:
- Add
--max-time 120to curl for long-running tasks (video/image generation)
On Windows cmd: Use %LINKAI_API_KEY% instead of $LINKAI_API_KEY.
Example (via bash tool):
bash(command='curl -sS --max-time 120 -X POST "https://api.link-ai.tech/v1/chat/completions" -H "Content-Type: application/json" -H "Authorization: Bearer $LINKAI_API_KEY" -d "{\"app_code\":\"G7z6vKwp\",\"messages\":[{\"role\":\"user\",\"content\":\"What is AI?\"}],\"stream\":false}"', timeout=130)Response
Success (extract choices[0].message.content from JSON):
{
"choices": [{
"message": {
"role": "assistant",
"content": "AI stands for Artificial Intelligence..."
}
}],
"usage": {
"prompt_tokens": 10,
"completion_tokens": 50,
"total_tokens": 60
}
}Error:
{
"error": {
"message": "Error description",
"code": "error_code"
}
}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.

