How do I install the Exploration Guided Unfamiliar App Adaptation skill?

Run npx skillmds@latest add dingxingdi/exploration-guided-unfamiliar-app-adaptation-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Exploration Guided Unfamiliar App Adaptation safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Exploration Guided Unfamiliar App Adaptation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Exploration Guided Unfamiliar App Adaptation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Exploration Guided Unfamiliar App Adaptation?

dingxingdi (@dingxingdi) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Exploration Guided Unfamiliar App Adaptation by dingxingdi

Name: Exploration Guided Unfamiliar App Adaptation
Author: dingxingdi

Exploration Guided Unfamiliar App Adaptation

Use this skill when the user wants data where the agent must first learn a new app instead of relying on habits from familiar software. Trigger it for requests like “make it figure out a new app by looking around first,” “test whether it can adapt to an unfamiliar layout,” “have it explore before acting,” or “don’t let knowledge from another app transfer cleanly.” This skill is for GUI tasks where app-specific structure must be discovered from exploration traces before the real task can be solved.

dingxingdi Updated Sep 17, 2026

File contents

Skill: exploration-guided-unfamiliar-app-adaptation

1. Capability Definition & Real Case

Professional Definition: The capability to acquire actionable knowledge about an unfamiliar GUI environment through prior exploration and then use that knowledge to solve downstream tasks in the same application. The agent must convert exploration evidence into app-specific navigation priors, functional understanding, and route selection rather than over-relying on generic cross-app assumptions.
Dimension Hierarchy: GUI Perception and Environment Modeling->Environment Understanding->exploration-guided-unfamiliar-app-adaptation

Real Case

[Case 1]

Initial Environment: A messaging-and-payment super-app is open on its home screen. The agent has access to an exploration trace showing how wallet, payment, and subscription-management pages are organized, but the target feature is not exposed from the initial view and the app’s information architecture does not mirror common Western payment apps.
Real Question: Please cancel auto-payment service in WeChat.
Real Trajectory: Consult the exploration trace, infer that the relevant path runs through wallet and payment management rather than a generic settings page, navigate to the auto-renewal area, identify the active service, and cancel it.
Real Answer: The auto-payment service is canceled.
Why this demonstrates the capability: The task is difficult precisely because prior experience with other payment apps can suggest the wrong route. Success depends on mining the exploration evidence for app-specific structure, then translating that evidence into a correct action sequence in the unfamiliar app. That is the defining pattern of exploration-guided adaptation.

Pipeline Execution Instructions

To synthesize data for this capability, you must strictly follow a 3-phase pipeline. Do not hallucinate steps. Read the corresponding reference file for each phase sequentially:

Phase 1: Environment Exploration Read the exploration guidelines to discover raw knowledge seeds: references/EXPLORATION.md
Phase 2: Trajectory Selection Once Phase 1 is complete, read the selection criteria to evaluate the trajectory: references/SELECTION.md
Phase 3: Data Synthesis Once a trajectory passes Phase 2, read the synthesis instructions to generate the final data: references/SYNTHESIS.md

---name: exploration-guided-unfamiliar-app-adaptation-2description: Use this skill when the user wants data where the agent must first learn a new app instead of relying on habits from familiar software. Trigger it for requests like “make it figure out a new app by looking around first,” “test whether it can adapt to an unfamiliar layout,” “have it explore before acting,” or “don’t let knowledge from another app transfer cleanly.” This skill is for GUI tasks where app-specific structure must be discovered from exploration traces before the real task can be solved.---# Skill: exploration-guided-unfamiliar-app-adaptation## 1. Capability Definition & Real Case* **Professional Definition**: The capability to acquire actionable knowledge about an unfamiliar GUI environment through prior exploration and then use that knowledge to solve downstream tasks in the same application. The agent must convert exploration evidence into app-specific navigation priors, functional understanding, and route selection rather than over-relying on generic cross-app assumptions.* **Dimension Hierarchy**: GUI Perception and Environment Modeling->Environment Understanding->exploration-guided-unfamiliar-app-adaptation### Real Case**[Case 1]*** **Initial Environment**: A messaging-and-payment super-app is open on its home screen. The agent has access to an exploration trace showing how wallet, payment, and subscription-management pages are organized, but the target feature is not exposed from the initial view and the app’s information architecture does not mirror common Western payment apps.* **Real Question**: Please cancel auto-payment service in WeChat.* **Real Trajectory**: Consult the exploration trace, infer that the relevant path runs through wallet and payment management rather than a generic settings page, navigate to the auto-renewal area, identify the active service, and cancel it.* **Real Answer**: The auto-payment service is canceled.* **Why this demonstrates the capability**: The task is difficult precisely because prior experience with other payment apps can suggest the wrong route. Success depends on mining the exploration evidence for app-specific structure, then translating that evidence into a correct action sequence in the unfamiliar app. That is the defining pattern of exploration-guided adaptation.## Pipeline Execution InstructionsTo synthesize data for this capability, you must strictly follow a 3-phase pipeline. **Do not hallucinate steps.** Read the corresponding reference file for each phase sequentially:1. **Phase 1: Environment Exploration** Read the exploration guidelines to discover raw knowledge seeds: `references/EXPLORATION.md`2. **Phase 2: Trajectory Selection** Once Phase 1 is complete, read the selection criteria to evaluate the trajectory: `references/SELECTION.md`3. **Phase 3: Data Synthesis** Once a trajectory passes Phase 2, read the synthesis instructions to generate the final data: `references/SYNTHESIS.md`

Frequently asked questions