Search: "proposal"

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

Prepares evidence-bounded, constructive peer-review drafts and structured manuscript assessments. Supports authorized review of scientific manuscripts, protocols, preprints, or research proposals; reporting-guideline selection; claim–evidence checks; methods, statistics, reproducibility, ethics, figure/table, and citation critique; or revision-response planning.

Supports research proposal preparation and review for NSF, NIH, DOE, DARPA, and Taiwan NSTC, including opportunity-specific requirements, aims, review criteria, budgets, broader impacts, forms, and resubmissions. Use for investigator-authored grant development, compliance matrices, and proposal critiques.

Selects bounded, graph-informed source slices with Trailmark and delegates focused code analysis or patch-proposal work to a smaller subagent. Use when offloading function-, class-, caller-, callee-, call-path-, entrypoint-, or line-focused code tasks to constrained or locally hosted models without exposing the full repository.

How to improve an existing ad account with Adako, the MCP server and REST API that connects this assistant to Google Ads, Meta Ads, ChatGPT Ads, TikTok Ads and LinkedIn Ads. Use it whenever the user asks to cut wasted spend, add negative keywords, reallocate or raise budgets, change a bid strategy, fix placements or audiences, pause what is not working, or asks "what should I do about this account". It gives the order to work in, which diagnosis tool feeds which change, how to size a change, how to phrase the proposal, and what to leave alone.

Operating procedure for Adako, the MCP server and REST API that connects this assistant to the user's Google Ads, Meta Ads, LinkedIn Ads and ChatGPT Ads accounts (TikTok Ads tools are listed but not available yet). Use it whenever the user asks about ad spend, performance, campaigns, ad sets, ad groups, keywords, search terms, audiences, budgets, pixels, creatives, monitors or briefs on those platforms, and whenever they ask to create, pause, resume, re-budget or otherwise change anything in those accounts. It defines the safety contract (read before write, every write becomes a proposal the user approves, created objects are always paused), the tool-call contract (233 tools, read routers for lookups and _write routers for changes, ids are strings, budgets are decimals in the account currency, dates are YYYY-MM-DD or a preset), the tool map per platform, and the standard workflows for performance reviews, wasted-spend cleanup, campaign launches, monitors, approvals and error recovery. Do not use it for platforms Adako does not cover.

How to launch a new campaign safely with Adako, the MCP server and REST API that connects this assistant to Google Ads, Meta Ads, ChatGPT Ads, TikTok Ads and LinkedIn Ads. Use it whenever the user asks to create, launch, set up or draft a campaign, ad group, ad set or ad on any of those platforms, or asks what a launch needs before it can go live. It gives the pre-flight checks, the resolver calls that must run before any write, the create tool and minimum budget per platform, what the proposal must show, and how to read a launch back and verify it.

How to improve an existing ad account with Adako, the MCP server and REST API that connects this assistant to Google Ads, Meta Ads, ChatGPT Ads, TikTok Ads and LinkedIn Ads. Use it whenever the user asks to cut wasted spend, add negative keywords, reallocate or raise budgets, change a bid strategy, fix placements or audiences, pause what is not working, or asks "what should I do about this account". It gives the order to work in, which diagnosis tool feeds which change, how to size a change, how to phrase the proposal, and what to leave alone.

Operating procedure for Adako, the MCP server and REST API that connects this assistant to the user's Google Ads, Meta Ads, LinkedIn Ads and ChatGPT Ads accounts (TikTok Ads tools are listed but not available yet). Use it whenever the user asks about ad spend, performance, campaigns, ad sets, ad groups, keywords, search terms, audiences, budgets, pixels, creatives, monitors or briefs on those platforms, and whenever they ask to create, pause, resume, re-budget or otherwise change anything in those accounts. It defines the safety contract (read before write, every write becomes a proposal the user approves, created objects are always paused), the tool-call contract (233 tools, read routers for lookups and _write routers for changes, ids are strings, budgets are decimals in the account currency, dates are YYYY-MM-DD or a preset), the tool map per platform, and the standard workflows for performance reviews, wasted-spend cleanup, campaign launches, monitors, approvals and error recovery. Do not use it for platforms Adako does not cover.

Operating procedure for Adako, the MCP server and REST API that connects this assistant to the user's Google Ads, Meta Ads, LinkedIn Ads and ChatGPT Ads accounts (TikTok Ads tools are listed but not available yet). Use it whenever the user asks about ad spend, performance, campaigns, ad sets, ad groups, keywords, search terms, audiences, budgets, pixels, creatives, monitors or briefs on those platforms, and whenever they ask to create, pause, resume, re-budget or otherwise change anything in those accounts. It defines the safety contract (read before write, every write becomes a proposal the user approves, created objects are always paused), the tool-call contract (233 tools, read routers for lookups and _write routers for changes, ids are strings, budgets are decimals in the account currency, dates are YYYY-MM-DD or a preset), the tool map per platform, and the standard workflows for performance reviews, wasted-spend cleanup, campaign launches, monitors, approvals and error recovery. Do not use it for platforms Adako does not cover.

How to launch a new campaign safely with Adako, the MCP server and REST API that connects this assistant to Google Ads, Meta Ads, ChatGPT Ads, TikTok Ads and LinkedIn Ads. Use it whenever the user asks to create, launch, set up or draft a campaign, ad group, ad set or ad on any of those platforms, or asks what a launch needs before it can go live. It gives the pre-flight checks, the resolver calls that must run before any write, the create tool and minimum budget per platform, what the proposal must show, and how to read a launch back and verify it.