Reduce unnecessary prompts in X skills

Author: shinshin86

skills/x-act-on-notifications/SKILL.md

@@ -7,7 +7,7 @@ description: Perform selected actions on X (Twitter) notifications through ai-ch
 
 Use ai-chrome-pilot to inspect X notifications, build a candidate list, and perform only the requested action on the notifications that match the user's criteria.
 
-Keep the skill profile-agnostic. Ask for the profile name at runtime instead of hardcoding any specific profile.
+Keep the skill profile-agnostic. Use `default` unless the user explicitly requested another profile.
 
 Use this skill for notification actions. If the user only wants to inspect notifications first, use `x-get-notifications` instead. If the user wants to reply or quote-post from a target post, use `x-compose-post`.
 
@@ -28,17 +28,25 @@ Do not overload this skill with reply or quote composition. Treat those as posti
 
 If X shows a login screen, stop and use `x-login` first.
 
-## Inputs To Confirm
+## Inputs To Resolve
 
-Confirm these before acting:
+Resolve these before acting:
 
 - `profile_name`: default to `default` if unspecified
 - `action`: one of `like`, `bookmark`, `repost`
 - `types`: `reply`, `quote`, or both
 - `filters`: actor handle/name, text substring, date substring, and optional limit
 - `mode`: `dry-run` or `execute`
 
-If the user says only "interact with notifications" without enough detail, default to `dry-run` and present candidates first instead of clicking anything.
+Default resolution rules:
+
+- If `profile_name` is unspecified, use `default` without asking
+- If the user explicitly asked to `like` or `bookmark`, default `mode=execute`
+- If the user explicitly asked to `repost`, default `mode=dry-run` unless the request already includes clear matching conditions
+- If `types` is unspecified, inspect both `reply` and `quote`
+- If `filters` is unspecified and the action is `like` or `bookmark`, treat the request as applying to all matching pending notifications currently collected
+
+If the user says only "interact with notifications" without enough detail to infer an action, default to `dry-run` and present candidates instead of clicking anything.
 
 Recommended decision rule:
 
@@ -136,7 +144,10 @@ Useful filter patterns:
 
 If multiple candidates still match and the user asked for one specific item, stop and show the narrowed list instead of acting.
 
-If no explicit filters were supplied, propose a candidate list grouped by reply and quote, then wait for confirmation unless the user clearly asked to act on all matching unacted notifications of a broad class.
+If no explicit filters were supplied:
+
+- for `like` or `bookmark`, execute against all matching pending notifications when the user clearly asked to perform that action
+- for `repost`, present the candidate list first unless the request already identifies the target notifications unambiguously
 
 ### 6. Execute the requested action
 
@@ -182,7 +193,8 @@ Report:
 
 - Never hardcode a profile name
 - Never act on anything if the matching logic is ambiguous
-- Prefer `dry-run` first unless the user clearly requested execution
+- Do not ask follow-up questions when the action, scope, and target notifications are already explicit enough to execute safely
+- Prefer `dry-run` first for `repost` or when the requested action cannot be matched unambiguously
 - Use fresh refs from the latest `/snapshot`; do not reuse stale refs after scrolling or clicking
 - Check both tabs before saying there are no matches
 - Treat `repost` as higher-risk than `like` or `bookmark`; stop if any confirmation step is unclear

skills/x-compose-post/SKILL.md

@@ -9,7 +9,7 @@ Use ai-chrome-pilot to create X posts from one unified workflow, then branch int
 
 Prefer this skill for all post-creation tasks. Use `x-schedule-post` only when a schedule-only flow is explicitly needed.
 
-Keep the skill profile-agnostic. Ask for the profile name at runtime instead of hardcoding any profile.
+Keep the skill profile-agnostic. Use `default` unless the user explicitly requested another profile.
 
 ## Prerequisites
 
@@ -20,9 +20,9 @@ Keep the skill profile-agnostic. Ask for the profile name at runtime instead of
 
 If X shows a login screen, stop and use `x-login` first.
 
-## Inputs To Confirm
+## Inputs To Resolve
 
-Confirm these before acting:
+Resolve these before acting:
 
 - `profile_name`: default to `default` if unspecified
 - `mode`: one of `post`, `reply`, `quote`, `schedule`
@@ -33,6 +33,13 @@ Confirm these before acting:
   - year, month, day, hour, minute
 - `image`: optional attachment path when the user provided one
 
+Default resolution rules:
+
+- If `profile_name` is unspecified, use `default` without asking
+- If the request is a normal post and includes `post_text`, execute directly
+- If the request is a scheduled post and includes `post_text` plus the full schedule, execute directly
+- If the request is `reply` or `quote`, ask only when the target post is not specific enough to identify safely
+
 If the target post is not specific enough for `reply` or `quote`, stop and ask for clarification or first use a read-only skill to identify the exact target.
 
 ## Mode Selection
@@ -179,6 +186,7 @@ curl -s -X POST http://127.0.0.1:3333/eval \
 
 - Never hardcode a profile name
 - Never guess the target post for `reply` or `quote`
+- Do not ask for an extra confirmation immediately before submission when the mode, text, and target are already explicit
 - Prefer direct target URLs when the user supplied them
 - Stop when multiple similar posts match and the target is ambiguous
 - Use fresh refs from the latest `/snapshot`

skills/x-get-notifications/SKILL.md

@@ -17,17 +17,17 @@ Keep this skill read-only. Do not like, repost, reply, or otherwise engage with
 
 ## Steps
 
-### 1. Ask the user for profile name
+### 1. Resolve the profile name
 
-Ask which profile name to use (default is `default`). This determines which browser profile to load.
+Use `default` unless the user explicitly requested another profile. This determines which browser profile to load.
 
 ### 2. Verify server is running
 
 ```bash
 curl -s http://127.0.0.1:3333/health
 ```
 
-If not running, start it:
+If not running, start it with the resolved profile:
 
 ```bash
 HEADLESS=0 PROFILE_NAME=<profile_name> npx tsx src/index.ts &
@@ -109,6 +109,7 @@ kill $(lsof -ti:9222) 2>/dev/null
 
 ## Important notes
 
+- Do not ask which profile to use unless the user explicitly needs a non-`default` profile
 - Add `sleep 1-2` between operations to wait for page loads
 - Always use `/snapshot` before each action to get fresh refs
 - The notifications page may require scrolling to load all notifications (infinite scroll)

skills/x-login/SKILL.md

@@ -15,9 +15,9 @@ Log in to X via ai-chrome-pilot and persist the session to a browser profile.
 
 ## Steps
 
-### 1. Ask the user for a profile name
+### 1. Resolve the profile name
 
-Ask which profile name to use (default is `default`). The profile determines where browser data is stored (`~/.ai-chrome-pilot/profiles/<profile_name>/`).
+Use `default` unless the user explicitly requested another profile. The profile determines where browser data is stored (`~/.ai-chrome-pilot/profiles/<profile_name>/`).
 
 ### 2. Start the server
 
@@ -57,7 +57,7 @@ View `/tmp/x_login_check.png` with the Read tool.
 
 ### 6. Request manual login if needed
 
-If not logged in, **ask the user to log in manually**. Never attempt to enter credentials automatically.
+If not logged in, ask the user to log in manually in the opened browser window. Never attempt to enter credentials automatically.
 
 Example message:
 > The Chrome browser window is open. Please log in to X in the browser. Let me know when you're done.
@@ -75,5 +75,6 @@ After successful login, inform the user:
 
 ## Important notes
 
+- Do not ask which profile to use unless the user explicitly needs a non-`default` profile
 - Always ask the user to log in manually. Never auto-fill passwords or authentication credentials.
 - Do not use `EPHEMERAL=1` if the session needs to be persisted.

skills/x-schedule-post/SKILL.md

@@ -17,11 +17,16 @@ Treat this as the schedule-focused variant of `x-compose-post`. If the user want
 
 ## Required inputs
 
-Ask the user for:
 - **Post text**: The text to post
 - **Scheduled date/time**: Year, month, day, hour, and minute
 - **Image** (optional): An image to attach
 
+Default resolution rules:
+
+- Use `default` unless the user explicitly requested another profile
+- If post text and the full scheduled date/time are already provided, execute directly without an extra confirmation step
+- Ask follow-up questions only when required inputs are missing
+
 ## Steps
 
 ### 1. Verify server is running
@@ -30,7 +35,7 @@ Ask the user for:
 curl -s http://127.0.0.1:3333/health
 ```
 
-If not running, start it:
+If not running, start it with the resolved profile:
 
 ```bash
 HEADLESS=0 PROFILE_NAME=<profile_name> npx tsx src/index.ts &
@@ -186,6 +191,7 @@ kill $(lsof -ti:9222) 2>/dev/null
 
 ## Important notes
 
+- Do not ask which profile to use unless the user explicitly needs a non-`default` profile
 - Add `sleep 1-2` between operations to wait for page loads
 - Always use `/snapshot` before each action to get fresh refs (refs change when the page navigates or dialogs open/close)
 - X's UI is dynamic; use both snapshots and screenshots to identify the correct elements