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

Explore SkillOpt for improving Cursor agent skills from our session data

Open
#111 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 4 days

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reviewing SkillOpt's documented input and validation flow, then inspect the local AGENTS.md, .cursor/agents/, shared skills, and ~/.cursor/projects/*/agent-transcripts/ layout. Compare those inputs with the existing skill-creator eval loop. Done means a documented fit decision, a scoped Cursor transcript adapter proposal, and concrete evaluation, privacy, and cost criteria.

Written by the indexing model from the issue text.

Description

We use Cursor heavily on our system (and related repos) with AGENTS.md, .cursor/agents/, and shared skills.

Our session transcripts live locally under ~/.cursor/projects/*/agent-transcripts/.

Microsoft SkillOpt looks like a way to improve those skill documents from real usage — with validation so changes only land when they actually help.

Ask: Is this worth pursuing for our setup? SkillOpt doesn’t appear to support Cursor transcripts out of the box, so we’d need some adapter work.

Questions to answer:

  • Does SkillOpt fit how we work, or is our existing skill-creator eval loop enough?
  • What would we optimize first — AGENTS.md, PR review agents, or domain skills?
  • How would we know a skill change is actually better (tests, lint, PR review quality)?
  • What’s the privacy/cost tradeoff of sending harvested session data to an optimizer API?
Dominant language
Python
Stars
17.3k
Forks
1.6k
Avg merge
8d 16h
Merged PRs (30d)
11

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 microsoft/SkillOpt

All issues in microsoft/SkillOpt

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.