fix(kyberforge): fix template test docs, dangling skill ref, and README table consistency

- Rewrite assets/templates/tests/README.md with correct repo-root context and
  SKILL_NAME placeholder in bats run command (was: `bats tests/`, wrong CWD)
- Add sed substitution for tests/README.md in new-skill.sh so SKILL_NAME is
  replaced in scaffolded test docs; test added to new-skill.bats (red→green)
- Remove /write-eval reference from skill-improve SKILL.md; reword as direct
  action since the skill does not exist in the kyberforge plugin
- Remove self-referential README.md rows from skill-audit and skill-improve
  Files tables to match template and skill-write convention

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

plugins/kyberforge/skills/skill-improve/README.md

@@ -23,4 +23,3 @@ Provide the skill directory path and any signal files in the conversation. The s
 | File | Purpose |
 |------|---------|
 | `SKILL.md` | Skill instructions for agents |
-| `README.md` | Human-facing description of the skill and its files |

plugins/kyberforge/skills/skill-improve/SKILL.md

@@ -73,4 +73,4 @@ If a signal points to a script or reference file, edit that file directly rather
 
 Run `/skill-audit` on the skill directory. Resolve any FAIL findings before considering the improvement complete.
 
-If the skill has no `evals/` directory, note it after the audit: "No evals found — consider running `/write-eval` to add test coverage so future improvement cycles have quantitative signals to work from."
+If the skill has no `evals/` directory, note it after the audit: "No evals found — consider adding an `evals/` directory with assertion-based test cases to give future improvement cycles quantitative signals to work from."