pdate skill damit er nicht immer die Belege mit aufschreibt

.github/skills/add-knowledge-from-repo/SKILL.md

@@ -48,7 +48,7 @@ Read all three files before making changes:
 
 Then update them in this order:
 
-1. **Projects:** Add or extend one project entry with project source, evidence-backed period where available, context, challenges, and solutions. For Git-less projects, state that the period is not specified and label user-confirmed authorship explicitly.
+1. **Projects:** Add or extend one project entry with project source, evidence-backed period where available, context, challenges, and solutions.
 2. **Roles:** Add or extend a role only where its context and responsibilities are supported. Avoid a role entry when the repository cannot substantiate one.
 3. **Technologies:** Add or extend individual technology entries. For every technology, include complexity, concrete usage, and the project/context.
 
@@ -59,7 +59,7 @@ Maintain existing headings, German language, and factual bullet style. Merge wit
 After updating all three Knowledge-Base files, update both files below. This is required when the repository produces at least one new, verified fact relevant to the current application.
 
 1. Read `letters/coverletter.tex`, `letters/cv.tex`, and the shared document entry points `latex/coverletter.tex` and `latex/cv.tex`.
-2. Determine the target role from the current cover letter. Select only newly documented facts that support this role and can be defended from repository evidence.
+2. Determine the target role from the current cover letter. Select only newly documented facts that support this role and can be defended from project based evidence.
 3. Update `letters/coverletter.tex` with one or two concise, concrete examples that connect the new facts to the target role. Clearly label private work as private where relevant.
 4. Update `letters/cv.tex` with concise, recruiter-scannable evidence, such as a suitable skills entry or a project-related bullet. Do not add a duplicate role merely to force the fact into the CV.
 5. Update both documents in the same run. Do not update only the Knowledge Base or only one letter when relevant new facts exist.