Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Local RAG implementation for skills discovery when they grow past a certain limit

Open
#212 7 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
python
Domain
ai

Research direction

Start with the skills implementation in pull request #206 and the related discussion in issue #170. Compare local RAG and subagent approaches, then clarify the design, integration points, and measurable criteria for reducing injected skill context before implementation begins.

Written by the indexing model from the issue text.

Description

enhancement help wanted priority normal
How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Feature request

Which Nextcloud Version are you currently using: 34.0.0

Is your feature request related to a problem? Please describe.
The skills' names and descriptions are extracted and put in the context of the model for the skills discovery by the model. For 20 skills, this could roughy take 5500 tokens, or 2750 tokens on average (see https://github.com/nextcloud/context_agent/issues/170#issuecomment-4945087989).
But skills have many uses from documentation for process automation to document writing adapted from a style, not to mention they are combined with the admin provided skills too. See https://github.com/nextcloud/context_agent/issues/170#issuecomment-4947934711

Describe the solution you'd like
One of the ideas could be to use local RAG to not inject everything but provide skill results to the model based on need.
The other would be to use subagents that will see all the skills (maybe could also be implemented for tools) and respond with the appropriate ones, which the main model can then call directly.

Describe alternatives you've considered

  1. Limiting the no. of skills injected
  2. Only injecting the skills names instead of names + short descriptions

Additional context
Skills PR: https://github.com/nextcloud/context_agent/pull/206
Discussion: https://github.com/nextcloud/context_agent/issues/170

Dominant language
Python
Stars
25
Forks
16
Avg merge
2d 14h
Merged PRs (30d)
6

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nextcloud/context_agent

All issues in nextcloud/context_agent

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.