Set up ChatGPT in one day Sam Cherkasov https://www.sam-cherkasov.com/lead-magnets/chatgpt-setup-guide Save the guide and templates. Replace every [bracketed field] before using a prompt. 1. Desktop app / Your first useful result Read the meeting notes I attached. Create a short action list with these columns: action, owner, deadline, and source quote. Use only the notes. If an owner or deadline is missing, write ‘not specified’. End with the three questions I need to resolve next. Return the draft here for review. ================================================ 2. One project / Project instructions Help me with [one recurring area of work]. My role: [what I do] My audience or clients: [who the work is for] My current goal: [one concrete result] My constraints: [time, budget, format, language] My source files: [file names and what each contains] My preferred style: [tone + two examples] Use my source files before making assumptions. Ask up to 3 questions when missing information would change the result. Do not invent facts, results, or commitments. Separate what the sources say from your suggestions. Return a usable draft, then list the decisions I need to make. Keep answers concise unless I ask for detail. ================================================ 2. One project / Test your project context Using only this project’s instructions and sources, summarize who I’m creating work for, my current goal, and the constraints you should follow. Point to the relevant source for each. Tell me what information is still missing. ================================================ 3. Connected apps / Check one connected source Use my connected Google Drive to find the latest document titled [document title] in [folder, if known]. If there are several matches, show their titles and dates and ask me which one to use. Summarize the chosen document in five bullets. Include a link to it and quote the sentence supporting each bullet. Do not edit or share the document. ================================================ 4. One skill / Create your first skill Create an instruction-only skill named content-ideas. Use it when I ask to turn a rough note, customer question, or work observation into content ideas. Do not use it for unrelated writing. Before creating it, ask me for my audience, main topic, language, and two examples of content I like. The workflow: 1. Read my note and any relevant project context. 2. Ask up to 3 questions if key context is missing. 3. Return exactly 5 distinct ideas. For each, include an angle, a one-sentence hook, the reader’s practical takeaway, and a suitable format. 4. Recommend one idea and explain why it fits my audience. Use short, conversational language. Avoid vague AI hype, unsupported statistics, and invented personal stories. Keep facts from my note separate from suggested angles. Show me the finished instructions before saving. Do not publish or message anyone. ================================================ 4. One skill / Test the saved skill Use my content-ideas skill. My rough note: [paste a real observation or audience question]. Follow the saved workflow. Ask for any missing context, then give me five distinct ideas and recommend one. ================================================ 5. Scheduled task / Schedule a useful briefing Every Monday at 08:30 in [timezone, e.g. Europe/Madrid], return to this chat and prepare a briefing on [specific topic] covering the last 7 days. Use current, accessible primary sources. Include up to 3 meaningful developments, with the event date, source link, and a sentence on why each matters for [my work]. End with one practical thing to consider. Keep the briefing under 200 words. If nothing relevant changed, say so instead of padding the list. If a source cannot be accessed, state the gap. Before saving, show me the schedule, timezone, and tools the task will use. ================================================ A quieter way to monitor something Every weekday at 09:00 in [timezone], check [one public URL] for [the specific change I care about]. Return to this chat for each check. On the first run, record the current relevant information as the baseline and confirm it once. On later runs, compare with the last successful check. Notify me only if [clear change condition] happens or access fails. Stay quiet when nothing actionable changes. When reporting a change, show what changed, the previous value, the new value, the source URL, and the check time. Do not interpret a failed page load as a change. Show me the schedule and baseline approach before saving.