agentleFS
OpenLinkSoftwareOpenLinkSoftware/ai-agent-skills/opal-agent-skill-assembler/SKILL.md

opal-agent-skill-assembler

Skill42 starsChanged 50 days agoMITView on GitHub

Assemble or exercise OPAL Agents and Skills. Trigger on phrases like 'assemble an agent', 'create an AGENTS.md', 'build a skill', 'exercise an agent', 'test a skill', 'list OPAL agents', 'instantiate an agent', or any request to work with OPAL agents, skills, or function tools.

  • Sends data out

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    All endpoints are constructed as https://{host}/chat/api, https://{host}/listAgents, etc.

    line 28
  2. Distinctive:

    Ask the user to choose:

    line 32
  3. Very specific:

    OAuth 2.1: Run Authorization Code flow (see preferences.ttl howto for OAuth flow).

    line 33
  4. Distinctive:

    Ask for: agent ID, title, version, optional model key override

    line 52
  5. Distinctive:

    Ask for: skill ID, title, version

    line 61
  6. Distinctive:

    Ask for optional model API key override and test prompt text (default: "Introduce yourself and your capabilities.")

    line 71
  7. Distinctive:

    After assembly or exercise:

    line 115

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

OPAL Agent & Skill Assembler

Dual-purpose skill for working with OPAL (OpenLink AI Layer) agents, skills, and function tools. Assemble new agent/skill configurations or exercise existing ones against any OPAL endpoint.

What OPAL Provides

OPAL exposes /chat/api on any OPAL-enabled Virtuoso instance. An Agent orchestrates one or more Skills; a Skill bundles one or more Tools (functions). See references/opal-service-surface.md for the full API surface.

Elicitation Flow

1. OPAL Endpoint

Present these options and ask the user to choose or enter a custom host:

ShortcutHost
URIBurnerlinkeddata.uriburner.com
Demodemo.openlinksw.com
NetID QAnetid-qa.openlinksw.com
ODS-QAods-qa.openlinksw.com
Custom(enter any hostname)

All endpoints are constructed as https://{host}/chat/api, https://{host}/listAgents, etc.

2. Authentication

Ask the user to choose:

  • OAuth 2.1: Run Authorization Code flow (see preferences.ttl howto for OAuth flow). Use dynamic client registration at https://{host}/OAuth2/register, capture code on localhost:12345/callback, exchange for Bearer token.
  • API Key: Prompt user to paste their Bearer token directly.

3. Mode

Ask the user to choose:

ModeWhat it does
Assemble AgentList Skills → select → generate AGENTS.md + JSON → upload to WebDAV
Assemble SkillList Tools → select → generate SKILLS.md + JSON → upload to WebDAV
Exercise AgentList Agents → select one → instantiate → send test prompt → report
Exercise SkillList Skills → select one → instantiate → send test prompt → report

4A. Assemble Mode Details

Agent Assembly:

  1. GET https://{host}/listSkills — fetch available skills
  2. Present skills as a multi-select list with their descriptions
  3. Ask for: agent ID, title, version, optional model key override
  4. Generate AGENTS.md using prompts/agents-md-template.md
  5. Generate companion .json per references/opal-agent-skill-json-schema.md
  6. Offer to upload both to https://{host}/DAV/VAD/personal_assistant/json/{agent_id}.json and .../md/{agent_id}.md
  7. Provide curl commands for the upload

Skill Assembly:

  1. GET https://{host}/listFunctions — fetch available function tools
  2. Present tools as a multi-select list with descriptions
  3. Ask for: skill ID, title, version
  4. Generate SKILLS.md using prompts/skills-md-template.md
  5. Generate companion .json
  6. Offer to upload to WebDAV

4B. Exercise Mode Details

Exercise Agent:

  1. GET https://{host}/listAgents — fetch available agents
  2. Present as single-select list
  3. Ask for optional model API key override and test prompt text (default: "Introduce yourself and your capabilities.")
  4. Instantiate: POST https://{host}/chat/api with {"agent": "{selected_id}"} and the test message
  5. Display the response

Exercise Skill:

  1. GET https://{host}/listSkills — fetch available skills
  2. Same flow as agent exercise but with {"skills": ["{selected_id}"]}

OAuth Flow Reference

Per preferences.ttl howto (uriburner-oauth-authcode-flow.ttl):

# 1. Register client
curl -X POST https://{host}/OAuth2/register \
  -H "Content-Type: application/json" \
  -d '{"client_name":"OPAL Assembler","redirect_uris":["http://localhost:12345/callback"],"grant_types":["authorization_code"],"token_endpoint_auth_method":"none"}'

# 2. Authorize (open browser)
open "https://{host}/OAuth2/authorize?response_type=code&client_id={client_id}&redirect_uri=http://localhost:12345/callback&scope=openid"

# 3. Exchange code for token
curl -X POST https://{host}/OAuth2/token \
  -d "grant_type=authorization_code&code={code}&redirect_uri=http://localhost:12345/callback&client_id={client_id}&client_secret={client_secret}"

WebDAV Upload

# Upload AGENTS.md / SKILLS.md
curl -X PUT https://{host}/DAV/VAD/personal_assistant/md/{id}.md \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: text/markdown" \
  --data-binary @{local_file}

# Upload JSON companion
curl -X PUT https://{host}/DAV/VAD/personal_assistant/json/{id}.json \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  --data-binary @{local_file}

Verification

After assembly or exercise:

  • Assemble: confirm both .md and .json exist at the WebDAV paths
  • Assemble: GET https://{host}/listAgents (or /listSkills) should include the newly created agent/skill
  • Exercise: confirm the instantiated session returns a meaningful response

References

  • references/opal-service-surface.md — full OPAL API surface
  • references/opal-agent-skill-json-schema.md — JSON registration format
  • OPAL Playground: https://linkeddata.uriburner.com/chat/api
  • OAuth howto: preferences.ttl → howto/uriburner-oauth-authcode-flow.ttl

License

AGPL-3.0

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.