intel/dokimi
Dokimi (Greek δοκιμή, "test, proof") measures whether a skill, MCP doc source, agent profile or repository guidance actually helps a coding agent: paired on/off arm comparisons, novel-vs-known content analysis, and repository scans with graded agent runs.
Is intel/dokimi beginner-friendly?
In the last 30 days, intel/dokimi merged 163 of 193 pull requests from outside contributors, and its maintainers usually reply within 1 day. 1 beginner-friendly issue is open now.
- Stars
- 8
- Forks
- 7
- Open beginner issues
- 1
- Indexed issues
- 21
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 167
- Dominant language
- Python
- License
- Apache-2.0
- Last GitHub push
- Oct 21, 2026
- Latest indexed
- Oct 14, 2026
- Contributing guide
- Contributing guide
- Code of conduct
- Code of conduct
- Beginner labels
- No beginner labels indexed
How to contribute to intel/dokimi
- Read the contributing guide first: it says how the maintainers want changes proposed, tested and reviewed.
- Read its code of conduct: it covers issues and pull requests as well as chat.
- Your contributions will be published under the project's Apache-2.0 license.
- Pick the open beginner-friendly issue below and comment that you want to work on it before you start.
Issues somebody may already be working on are listed last. List everything by date
-
Difficulty 5/5 Over a week Newbie friendliness 24/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 43/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 Half a day Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
judge-validity: validate the judge in the setting arms are scored — persist judge material by digestOpen
Difficulty 4/5 3-5 days Newbie friendliness 22/100
Maintainers usually reply within 1 day
-
Dependency DashboardOpen
Difficulty 4/5 3-5 days Newbie friendliness 8/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
User loop: eval engine contracts (plan/validate/compare/gate/record), 3 skills, GitHub ActionPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 5/5 Over a week Newbie friendliness 18/100
intel/dokimi#121 · 1 comment ·
Maintainers usually reply within 1 day
-
Repository evaluation: move the eval mechanics out of oneDAL dev/agent_evals into dokimiPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 5/5 Over a week Newbie friendliness 18/100
Maintainers usually reply within 1 day
-
Architecture cleanup: fix live bugs, then deepen the LLM, eval-record, novelty, arms and process modulesPossibly taken A pull request linked to this issue is open or already merged. Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 8/100
Maintainers usually reply within 1 day