Automated summary
This skill analyzes implementations of external libraries or non-Python code to understand their logic and map them to the Python project gwexpy.
Strengths
- Provides deep understanding of how installed libraries work
- Handles various file formats (Python, C++, text files like MEDM .adl)
- Highlights differences with the current gwexpy implementation
Limitations
- Requires the source code to be accessible and readable
- May be limited for binary files or very large codebases
- Relies on manual analysis, not automated
When integrating or adapting external code into gwexpy and you need to understand its data structures or algorithms in detail.
When the external API documentation is sufficient or you do not need to modify the implementation.
Security analysis
SafeThe skill only instructs reading and analyzing code files; no execution of shell commands or destructive operations.
No concerns found
How this analysis is madeExamples
Analyze the implementation of numpy's array reshape function from the installed library. Find the source code in the site-packages and explain the logic flow and key data structures.Read the C++ source file of a Python extension (e.g., a .so file's corresponding .cpp) to understand the data structures used for serialization. Map them to equivalent Python classes in gwexpy.name: analyze_code description: 外部ライブラリや他言語で書かれたコードの実装を分析する
Analyze External Code
This skill helps in understanding code outside of the main Python source tree.
Instructions
-
Locate Source:
- If analyzing an installed library: Find where it is installed (usually
.venv/lib/pythonX.X/site-packages/). - If analyzing non-Python code (e.g. C++, MEDM files): Find the files in the file tree.
- If analyzing an installed library: Find where it is installed (usually
-
Read and Analyze:
- Use
view_fileto read the implementation. - For binary files or unknown formats, try to find a parser or read as text if applicable (e.g. MEDM
.adlfiles are text). - Map the external logic to how it interacts with or should be implemented in
gwexpy.
- Use
-
Report:
- Explain the data structures, algorithms, or logic flow found.
- Highlight differences with the current
gwexpyimplementation.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/analyze-external-code-mmk3ni93/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/analyze-external-code-mmk3ni93' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/analyze-external-code-mmk3ni93/download' --output '.skill-downloads/analyze-external-code-mmk3ni93/SKILL.md.part' && mv '.skill-downloads/analyze-external-code-mmk3ni93/SKILL.md.part' '.skill-downloads/analyze-external-code-mmk3ni93/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/analyze-external-code-mmk3ni93/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.