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

Evals skill lacks the customization loader block its own body relies on

Open Beginner friendly
#2,334 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 11 days

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
96/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown
Domain
documentation

Research direction

Start with skills/Evals/SKILL.md, especially the customization-dependent text around line 79, and compare it with the standard loader block referenced in SkillSystem.md around line 95. Add the standard customization section after the frontmatter and verify its path and instructions match the Evals suite path.

Written by the indexing model from the issue text.

Description

Problem. skills/Evals/SKILL.md:79 sends identity-bound suites to LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Evals/Suites/, but the skill has no ## Customization loader block, so nothing loads that directory. Other public skills carry the standard block, and SkillSystem.md:95 describes it.

Proposed change. Add the standard block after the frontmatter.

Pseudo-diff.

+## Customization
+
+**Before executing, check for user customizations at:**
+`~/.claude/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Evals/`
+
+If this directory exists, load and apply any PREFERENCES.md, configurations, or resources found there. These override default behavior. If the directory does not exist, proceed with skill defaults.

Why canon benefits. It makes the skill consistent with its own text and with the skill-system contract.

Dominant language
TypeScript
Stars
19.4k
Forks
2.5k
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 danielmiessler/LifeOS

All issues in danielmiessler/LifeOS

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.