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

docs(skills): make technical research mandatory for unverified external behavior
CI / PowerShell tests on Ubuntu (push) Failing after 3s
Details
CI / CI configuration security checks (push) Successful in 4s
Details
CI / Capabilities and shell quality (push) Successful in 22s
Details
CI / Python tests and compilation (push) Successful in 23s
Details
CI / Build and inspect generated packages (push) Successful in 19s
Details
CI / Bash integration and installation guards (push) Failing after 22s
Details
CI / Installed client configuration smoke tests (push) Successful in 1m16s
Details
CI / QMD local search integration (push) Failing after 12m46s
Details

Browse Source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Julian lechnerandClaude Opus 5.5 committed 2026-10-08 12:56:29 +02:00
1 parent 36851c34e2
commit 3f51bc908e
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,16 +1,16 @@
---
name: technical-research
description: Use before implementation when an unfamiliar or changing technology, API, standard, or technical trade-off needs current evidence. Prefer primary sources; do not use for repository-only code discovery.
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).
---
# Technical Research
Use before implementation when an unfamiliar technology, API, current product behavior, or technical trade-off could change the solution.
Verify external technology before it shapes the solution. Do not rely on remembered API signatures, defaults, or version behavior when they could have changed.
## Workflow
1. Turn the implementation question into specific facts or decisions that need evidence.
2. Prefer current primary sources: official product documentation, standards, release notes, or the original research. Check version and date when behavior may have changed.
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.
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.
5. Recommend an option only when evidence supports it. Explain the deciding trade-off briefly.