agentleFS
Sign inStart free
dmzoneilldmzoneill/skills/inscope-research/SKILL.md

inscope-research

Skill2 starsChanged 19 days agoApache-2.0View on GitHub

Query Red Hat InScope AI assistants for internal documentation - App Interface, Clowder, Konflux, etc. Auto-selects best assistant or query specific one. Use when user says "InScope", "ask InScope", "internal docs".

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 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.

  • 2

    Very specific

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

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

    If expired or refresh_auth: inscope_auto_login(headless=true)

    line 31
  2. Very specific:

    If no assistants: inscope_ask(query=inputs.question, include_sources=true) — auto-select

    line 39

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

InScope Research

Query Red Hat InScope AI assistants for internal documentation.

Inputs

InputTypeDefaultPurpose
questionstringrequiredQuestion to ask
assistantsstring-Comma-separated: app-interface, clowder, konflux. Empty = auto.
refresh_authboolfalseForce re-auth before query

Persona

  • persona_load("developer") — InScope tools

Workflow

1. Load Persona

  • persona_load("developer")

2. Check Auth

  • inscope_auth_status() — check token validity
  • If expired or refresh_auth: inscope_auto_login(headless=true)

3. List Assistants (optional)

  • inscope_list_assistants() — available assistants

4. Query

  • If no assistants: inscope_ask(query=inputs.question, include_sources=true) — auto-select
  • If assistants: inscope_query(query=inputs.question, assistant=first_assistant, include_sources=true)

5. Parse Results

  • Extract answer, sources, assistant used
  • If unauthorized: learn_tool_fix("inscope_ask", "unauthorized", "Token expired", "Run inscope_auto_login()")
  • If timeout: learn_tool_fix("inscope_ask", "timeout", "Request timed out", "Retry with simpler question")

6. Log

  • memory_session_log("InScope research", "Question: {query[:80]}, Assistant: {assistant}")

MCP Tools

  • inscope_ask, inscope_query, inscope_list_assistants
  • inscope_auth_status, inscope_auto_login, inscope_save_token

Quick Examples

skill_run("inscope_research", '{"question": "How do I configure RDS for my ClowdApp?"}')
skill_run("inscope_research", '{"question": "Konflux release process", "assistants": "konflux"}')

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