fraujulian/MyAiConfiguration
1
0 Fork 0
Code Issues Pull Requests Actions Activity

docs(skills): require primary evidence for every technical lookup

Browse Source
This commit is contained in:
Julian lechner committed 2026-10-08 13:55:27 +02:00
1 parent f497a23aaa
commit d929c6df26
1 file changed
+4 -4
Download Patch File Download Diff File Expand all files Collapse all files
shared/skills/research/technical-research/SKILL.md
+4 -4
View File
@@ -1,18 +1,18 @@
--- ---
name: technical-research name: technical-research
description: MUST use before relying on an external library, API, tool, product version, or standard whose current behavior you have not verified in this session, and before choosing between technical options. Prefer primary sources. Not for repository code discovery (use repository-research). description: MUST use before EVERY external technology search or lookup, including documentation fetches, API and package queries, familiar technologies, and follow-up searches; also before relying on unverified external behavior or choosing technical options.
--- ---
# Technical Research # Technical Research
Verify external technology before it shapes the solution. Do not rely on remembered API signatures, defaults, or version behavior when they could have changed. Apply `research` and this skill before every external technology lookup, even when the topic or version was researched earlier. Reuse loaded instructions, but check scope and evidence for each lookup. Verify external technology before it shapes the solution.
## Workflow ## Workflow
1. Turn the question into specific facts or decisions that need evidence. When the question concerns how this repository already uses the technology, run `repository-research` first and research only what the code does not answer. 1. Turn the question into specific facts or decisions that need evidence. When the question concerns how this repository already uses the technology, run `repository-research` first and research only what the code does not answer.
2. Prefer current primary sources: official documentation, standards, release notes, or source code of the exact version in use. Check version and date when behavior may have changed. 2. Open primary sources: official documentation, standards, release notes, or source code of the exact version in use. Check version and date when behavior may have changed. Search snippets and secondary summaries locate evidence; inspect the primary source before relying on its claims. If unavailable, report the gap and qualify the conclusion.
3. Compare only viable options against the user's constraints, compatibility needs, security properties, and maintenance cost. 3. Compare only viable options against the user's constraints, compatibility needs, security properties, and maintenance cost.
4. Separate source-backed facts from interpretation. Record assumptions and any material evidence that is missing or conflicting. 4. Separate source-backed facts from interpretation. Record assumptions and any material evidence that is missing or conflicting.
5. Recommend an option only when evidence supports it. Explain the deciding trade-off briefly. 5. Recommend an option only when evidence supports it. Explain the deciding trade-off briefly.
Return concise findings with direct sources and an implementation-relevant conclusion. Do not implement the change. Finish only when sources support the answer or remaining gaps are explicit. Return concise findings with direct sources, applicable versions, and an implementation-relevant conclusion. Continue authorized implementation after resolving its research questions.