feat: add Appium troubleshooting skill

[JustasMonkev]

Summary

• refine appium-troubleshooting to stay in one driver path and start from the failing symptom instead of a broader classification flow
• trim the troubleshooting references into compact entry points that defer to official Appium docs first and keep a short community-search fallback for recurring cases
• update README.md and AGENTS.md so the troubleshooting workflow stays aligned with the driver-scoped behavior

Checks

• git diff --check
• manual scenario validation against the updated troubleshooting skill for:
  • UiAutomator2 socket hang up on Android 14 emulator
  • unknown-driver session creation failure
  • XCUITest real-device WebDriverAgent timeouts right after session start

All three scenario checks stayed in the correct driver path and reached a concrete next step without cross-driver drift.

Closing #9

[KazuCocoa]

What kind of checks/tests did you do complete with this skills? Could you add these in this description?

[KazuCocoa]

Also, could you let AI tools to follow existing skill's format like adding metadata

[KazuCocoa]

Could you split this PR into only for uia2, xcuitest etc so we can take a look at the individual driver basis

[JustasMonkev]

What kind of checks/tests did you do complete with this skills? Could you add these in this description?

I used this prompt

Act as the troubleshooting assistant under test. Base your responses on the current skill at /skills/appium-troubleshooting/SKILL.md and its references. Do not edit files.

Answer these three user scenarios exactly as the assistant would.

Scenario 1:
"My Android test on UiAutomator2 starts the app and then Appium throws socket hang up a few seconds later. I’m on Android 14 emulator. What should I do?"

Scenario 2:
"I’m not sure which driver is in use. The session just fails and the only thing I know is Appium says it can’t create a session. How do I troubleshoot it?"

Scenario 3:
"My iPhone real-device XCUITest run fails because WebDriverAgent builds, then commands start timing out right after session start. What should I check first?"

For each scenario, give the answer you would send to the user: concise but concrete, evidence-first, and aligned with the skill. Label them Scenario 1/2/3.

[JustasMonkev]

Could you split this PR into only for uia2, xcuitest etc so we can take a look at the individual driver basis

yes, I will do it

[KazuCocoa]

After reading this PR again, I wondered if we should minimize skills documentation to avoid unnecessary duplication for long term maintenance

[JustasMonkev]

Thanks for the detailed feedback! I have a tight schedule at the moment, so it may take me a couple of weeks to properly address all the comments — especially the structural questions around minimizing the skill docs. I'll get back to this as soon as I can.

[KazuCocoa]

Thank you! LG. This kind of guide will keep modifying/refined but it is helpful to put as the first step

[KazuCocoa]

Hi @JustasMonkev, congrats: the Appium project wants to compensate you for this contribution! Please reply to this comment mentioning @jlipps and @KazuCocoa and sharing your OpenCollective account name, so that we can initiate payment! Or let us know if you decline to receive compensation via OpenCollective. Thank you!

[JustasMonkev]

Hi @JustasMonkev, congrats: the Appium project wants to compensate you for this contribution! Please reply to this comment mentioning @jlipps and @KazuCocoa and sharing your OpenCollective account name, so that we can initiate payment! Or let us know if you decline to receive compensation via OpenCollective. Thank you!

Hey, @KazuCocoa @jlipps, the account profile
https://opencollective.com/justas1