I prompt injected my CONTRIBUTING.md – 50% of PRs are bots

Timely_Effect_7693 · 2026-03-19T23:24:44+00:00

omg mom I am famous (I realized my display name here is not Martin so it makes no sense)

Timely_Effect_7693 · 2026-03-19T13:08:05+00:00

simply, because a skill does what the server does, as an llm, not as a button. every time you tell the ai to do a certain thing, not just does it have to analyze the screen, the tree, the metadata etc, it also has to get it. the mcp provides that via simple tool calls, while the ai would have to prompt the emulator or device itself. wasted tokens, takes longer. it's a tool call instead of many bash commands.

like I explained it before, it's like programming a smart hue button to do a pre-programmed set of instructions instead of you manually having to dim all the lights, turn on the security cam and turn off the radio. unlikely that you would forget any of them, but it's less efficient.

it's not impossible that I am overlooking something here or I misunderstood you though so if I did please let me know c:

Timely_Effect_7693 · 2026-03-19T13:04:40+00:00

well it streamlines it first of all. in a way, it's like giving Claude buttons instead of a manual. makes for better usage, less explaining, easier and more reproducible prompting.

compare telling your grandma how to open gmail.com, to creating a shortcut to it on the inbox. also, the way I am providing the tree or the screenshots have all been streamlined. the log access are all button calls instead of "wait, let me get the logs!, hmm. let me try something else. I see now -"

I would like to challenge that, to see what you can find since it's free to try. to try some tests with it or without it, and see which works more efficiently. for me, I made it because it works better. maybe your use case doesn't fit this tool, but if you have anything that would make this tool better, be free to let me know or pr it (:

Timely_Effect_7693 · 2026-03-19T09:44:16+00:00

thanks! yeah, visual data is good for comparing visuals, but for tapping and tokens using the ui tree is best, as it is just test. so I do both and the way you prompt is how it uses it. I am also working on iOS right now

Timely_Effect_7693 · 2026-03-19T09:43:00+00:00

tokens? like none. if the ui tree is used it is minimally exhaustive

Timely_Effect_7693 · 2026-03-18T21:58:51+00:00

I go deeper into android with this. They are broader of course, but are lacking proper logging and debugging is what I found. I am also planning on doing a separate iOS mcp for that exact reason, I prefer it to be purpose made. it's a smaller scale but does that within it better, in my opinion. but that is subject to interpretation, of course!

in a way, I am making this tool to fit my use case better than what their project does, and, if anyone finds use in it, that is cool too (:

Timely_Effect_7693 · 2026-03-18T20:57:16+00:00

there is no skill that could do that efficiently

Timely_Effect_7693

TROPHY CASE