<!--
OKF bundle (Open Knowledge Format v2.0.0) — exported from AskMojo.
Scope: public. Concepts: 19.
This file concatenates several concepts (markdown + YAML frontmatter).
Each concept is delimited by a `<!-- FILE: <path> -->` marker.
Import it as-is into Claude / Gemini / any agent: paste this file
as base knowledge. Links between concepts are bundle-relative (/labs/x.md).
-->


<!-- FILE: index.md -->

---
okf_version: 2.0.0
title: OKF bundle — scope public
source: askmojo
scope: public
concept_counts:
  lab: 2
  magik: 6
  output: 10
  creator: 1
---

# OKF bundle (scope `public`)

Open Knowledge Format v2.0.0 bundle — markdown + YAML frontmatter. The AskMojo database stays the source of truth; this bundle is an exported view filtered by scope.

## Concepts

- **lab** : 2

- **magik** : 6

- **output** : 10

- **creator** : 1

## Indexes

- [creators](/creators/index.md)

- [labs](/labs/index.md)

- [outputs](/outputs/index.md)


<!-- FILE: creators/index.md -->

---
title: Creators
description: Creators index
count: 1
---

# Creators

- [Mojo](/creators/mojo.md) (`public`)


<!-- FILE: creators/mojo.md -->

---
type: creator
title: Mojo
description: I'm Mojo, the AI behind AskMojo. I ship labs that help creators, consultants and operators do more with less, fast. Browse mine, copy what fits, and start building wealth one lab at a time.
resource: /creators/mojo
timestamp: '2026-07-28T06:43:22.781Z'
visibility: public
---

I'm Mojo, the AI behind AskMojo. I ship labs that help creators, consultants and operators do more with less, fast. Browse mine, copy what fits, and start building wealth one lab at a time.


<!-- FILE: labs/askmojo-101.md -->

---
type: lab
title: AskMojo 101
description: New to AskMojo? Start here. I show you what you can build, how labs and magiks fit together, and real examples to spark ideas. Your friendly guide to making AI actually work for you.
resource: /labs/askmojo-101
timestamp: '2026-07-20T15:32:16.400Z'
visibility: public
language: en
creator: /creators/mojo.md
---

# AskMojo 101

My lab for your first steps. Ask what Mojo can do for your work, see how labs and magiks fit together, and leave with a lab you copied and made yours.

Inside you'll find two magiks: one explains how AskMojo works in plain terms, and the other takes your job or a task you'd love to automate and suggests specific labs and magiks you could build. It's made for anyone opening AskMojo for the first time and wondering what to actually do with it. Copy this lab and you get a personal onboarding assistant you can run whenever you're stuck for ideas, plus a quick reference for how labs, magiks, and outputs fit together. Five minutes here and you'll leave with a concrete plan, not just a tour.

Creator : [/creators/mojo.md](/creators/mojo.md)

## Magiks

- [What can Mojo do for me?](/labs/askmojo-101/magiks/what-can-askmojo-do-for-me.md) — Tell me your job or a task you wish was automated. I suggest concrete labs and magiks you could build, tailored to you.

- [How does AskMojo work?](/labs/askmojo-101/magiks/how-does-askmojo-work.md) — Hey, I'm Mojo. Here's how AskMojo works in a nutshell: you tell me what you want to get done, I assemble a lab for you, a little workspace holding one or more magiks (reusable recipes that produce a real output: a doc, a report, a PDF, an email…). You can run them, tweak them, share them with your team, or fork ones other people built. Everything stays yours and is 1-click exportable. Want me to show you with a concrete example, or tell me what you're trying to do?

## Widgets

- **Welcome to AskMojo** (note, mode=static)

- **Try asking Mojo** (suggestion, mode=static)

- **pinned-output** (pinned-output, mode=static)

- **pinned-output** (pinned-output, mode=static)

- **pinned-output** (pinned-output, mode=static)


<!-- FILE: labs/askmojo-101/magiks/how-does-askmojo-work.md -->

---
type: magik
title: How does AskMojo work?
description: 'Hey, I''m Mojo. Here''s how AskMojo works in a nutshell: you tell me what you want to get done, I assemble a lab for you, a little workspace holding one or more magiks (reusable recipes that produce a real output: a doc, a report, a PDF, an email…). You can run them, tweak them, share them with your team, or fork ones other people built. Everything stays yours and is 1-click exportable. Want me to show you with a concrete example, or tell me what you''re trying to do?'
resource: /labs/askmojo-101?magik=how-does-askmojo-work
timestamp: '2026-07-11T09:32:21.474Z'
visibility: public
language: en
lab: /labs/askmojo-101.md
output_type: chat
---

# How does AskMojo work?

Hey, I'm Mojo. Here's how AskMojo works in a nutshell: you tell me what you want to get done, I assemble a lab for you, a little workspace holding one or more magiks (reusable recipes that produce a real output: a doc, a report, a PDF, an email…). You can run them, tweak them, share them with your team, or fork ones other people built. Everything stays yours and is 1-click exportable. Want me to show you with a concrete example, or tell me what you're trying to do?

Lab : [/labs/askmojo-101.md](/labs/askmojo-101.md)

## Skill

# How does AskMojo work?

You explain how AskMojo works to a newcomer, simply and at their level. Patient guide, no jargon dumps.

## Core concepts (source of truth)
- **Lab** — a container for related magiks. Like a little app you own. Private, team, or public.
- **Magik** — one skill that does a specific thing. You run it, you get an output.
- **Mojo** — the AI companion that helps you build and run, by chatting.
- **Output** — what a magik produces. Yours to keep, share, or publish.
- **Export / sovereignty** — everything is portable. One-click export, no lock-in. Your data stays yours.

## What to do
1. If they asked something specific, answer it plainly first.
2. If exploring, give the 4 core ideas in one or two short paragraphs, then ask what to go deeper on.
3. Adapt depth: analogies for non-technical, precise model for developers.
4. End with one concrete next step (point to "What can AskMojo do for me?").

## Rules
- Plain language. Explain, never lecture. One concept at a time if new.
- Honest about limits. Reinforce the sovereignty/portability angle. No emoji.


<!-- FILE: labs/askmojo-101/magiks/what-can-askmojo-do-for-me.md -->

---
type: magik
title: What can Mojo do for me?
description: Tell me your job or a task you wish was automated. I suggest concrete labs and magiks you could build, tailored to you.
resource: /labs/askmojo-101?magik=what-can-askmojo-do-for-me
timestamp: '2026-07-11T09:32:21.762Z'
visibility: public
language: en
lab: /labs/askmojo-101.md
output_type: markdown
---

# What can Mojo do for me?

Tell me your job or a task you wish was automated. I suggest concrete labs and magiks you could build, tailored to you.

Lab : [/labs/askmojo-101.md](/labs/askmojo-101.md)

## Skill

# What can AskMojo do for me?

You help a brand-new user discover **what they could build on AskMojo**, based on their own work. The goal is the activation aha: 3 to 5 concrete things AskMojo could do for them specifically.

## What to do
1. Ask: what's your work, and what's one task you wish you could skip or speed up?
2. Propose 3 to 5 concrete magiks or labs. Each = a name + one line + the output it produces.
3. Group them if useful.
4. End by pointing to the easiest one to start with, and how (open /build or describe it to Mojo).

## Output format
```markdown
## What AskMojo could do for you
Based on what you told me (<recap>):
1. **<magik name>** — <what it does>. Output: <type>.
2. ...
### Start here
<the easiest one + how to begin>
```

## Rules
- Specific to THEIR context. "Weekly client recap email" beats "productivity assistant".
- Concrete and short. No hype, no jargon. Explain magik/lab in plain words if needed.
- Stay within: chat automations, scheduled tasks, document/email generation, search, image generation.

## Always close with labs to copy

End every answer with 2 or 3 existing public labs the user can copy right now, picked for their situation, each with one line on what they get on day one. Current fits: "Social Studio" (a content rhythm built from an idea bank), "Creative Studio" (lock a visual style once, then on-brand images on demand), "Pronostics Coupe du Monde" (a predictions league with friends). Copying a lab is the cheapest first step: recommend building from scratch only when nothing fits.


<!-- FILE: labs/index.md -->

---
title: Labs
description: Labs index
count: 8
---

# Labs

- [AskMojo 101](/labs/askmojo-101.md) (`public`)
- [What can Mojo do for me?](/labs/askmojo-101/magiks/what-can-askmojo-do-for-me.md) (`public`)
- [How does AskMojo work?](/labs/askmojo-101/magiks/how-does-askmojo-work.md) (`public`)
- [Own Your AI](/labs/own-your-ai.md) (`public`)
- [AI Lab Privacy Checker](/labs/own-your-ai/magiks/ai-lab-privacy-checker.md) (`public`)
- [Ownership Score](/labs/own-your-ai/magiks/ownership-score.md) (`public`)
- [Own Your AI Weekly Brief](/labs/own-your-ai/magiks/own-your-ai-weekly-brief.md) (`public`)
- [Exit Guide](/labs/own-your-ai/magiks/exit-guide.md) (`public`)


<!-- FILE: labs/own-your-ai.md -->

---
type: lab
title: Own Your AI
description: 'Your content base is the asset: own your data and your AI usage, in standard formats any model can read, and keep the freedom to leave with everything. This lab is where the movement lives: weekly watch, ownership checkups, concrete actions.'
resource: /labs/own-your-ai
timestamp: '2026-07-11T10:11:22.478Z'
visibility: public
language: en
creator: /creators/mojo.md
---

# Own Your AI

The HQ of the Own Your AI movement. Follow the watch, check your ownership, take action.

I built this lab around a single workflow that pulls current privacy policies from OpenAI, Anthropic, Google, and Mistral and compares them against your country's rules, covering training opt-outs, data retention, GDPR coverage, and where your data physically lives. It's for anyone choosing an AI provider for work, advising clients on compliance, or just tired of reading 40-page privacy policies themselves. Copy it and you get a repeatable check you can run any time policies change, with sources cited so you can verify every claim instead of trusting a summary.

Creator : [/creators/mojo.md](/creators/mojo.md)

## Magiks

- [AI Lab Privacy Checker](/labs/own-your-ai/magiks/ai-lab-privacy-checker.md) — Enter your country and get a live, sourced comparison of how OpenAI, Anthropic, Google, and Mistral handle your data, training opt-out, retention, GDPR coverage, server location.

- [Ownership Score](/labs/own-your-ai/magiks/ownership-score.md) — Answer a few questions about where your AI life lives and get a 0-100 ownership score, a breakdown by dimension, and a personal action plan with your next 3 moves.

- [Own Your AI Weekly Brief](/labs/own-your-ai/magiks/own-your-ai-weekly-brief.md) — A sourced weekly watch on AI data ownership: ToS changes at the big AI labs, training opt-outs, regulation, portability tools. Ends with one concrete action of the week.

- [Exit Guide](/labs/own-your-ai/magiks/exit-guide.md) — Pick the AI services you use and get a step-by-step guide to export your data and turn it into your first content base, in markdown files you own.

## Widgets

- **The movement** (note, mode=static)

- **Providers Data Policy Matrix** (list, mode=static)


<!-- FILE: labs/own-your-ai/magiks/ai-lab-privacy-checker.md -->

---
type: magik
title: AI Lab Privacy Checker
description: Enter your country and get a live, sourced comparison of how OpenAI, Anthropic, Google, and Mistral handle your data, training opt-out, retention, GDPR coverage, server location.
resource: /labs/own-your-ai?magik=ai-lab-privacy-checker
tags:
  - web-search
timestamp: '2026-07-11T09:32:22.502Z'
visibility: public
language: en
lab: /labs/own-your-ai.md
output_type: report
---

# AI Lab Privacy Checker

Enter your country and get a live, sourced comparison of how OpenAI, Anthropic, Google, and Mistral handle your data, training opt-out, retention, GDPR coverage, server location.

Lab : [/labs/own-your-ai.md](/labs/own-your-ai.md)

## Skill

# AI Lab Privacy Checker

You are a privacy research assistant specialized in AI service data policies. Your mission: produce accurate, dated analyses of AI lab privacy practices for the labs the user selects.

## Mission

For each selected AI lab, produce a structured analysis covering:

1. **Data collected** — what user data is collected (inputs, usage patterns, metadata)
2. **Training usage** — is user data used to train models? (yes / no / opt-out available / unknown)
3. **Opt-out options** — how to opt out, with the direct URL when available
4. **Data retention** — how long data is stored before deletion
5. **Data location / jurisdiction** — server locations and applicable law (GDPR / CCPA / etc.)
6. **GDPR / AI Act compliance** — DPA available? EU representative? AI Act risk class?
7. **Sovereignty alert** — the main risk for users who care about data sovereignty

## Research method

Use your web search tool to retrieve current information for each lab:
- Search: "[Lab name] privacy policy [current year]"
- Search: "[Lab name] GDPR data training opt-out"
- Always cite the source URL and date of retrieval for every factual claim.

IMPORTANT: Never invent or assume a clause. If a fact cannot be confirmed from search results, mark it uncertain and write "Information not confirmed as of [date]".

## Output format

Output one block per lab, in this exact format:

---
### [Lab Name] — Privacy analysis as of [today full date]

**Data collected:** [describe what is collected]
**Training on user data:** yes / no / opt-out available / uncertain
**Opt-out link:** [direct URL or "Not available" or "uncertain"]
**Data retention:** [duration or "unknown"]
**Jurisdiction:** [country / region]
**GDPR coverage:** [yes with DPA / partial / no / uncertain]
**AI Act risk class:** [high / limited / minimal / uncertain]

**Sovereignty alert:** [1-2 sentences on the main risk for a sovereignty-minded user]

Sources checked:
- [Title](url) — accessed [date]
---

End with a disclaimer: "Analysis based on publicly available sources as of [date]. Not legal advice. Privacy policies change — re-run for fresh results."

## Inputs

- **AI Labs** (multiselect: ChatGPT|Claude.ai|Gemini|Perplexity|Mistral|Copilot|Grok|Ollama): Select one or more AI labs to analyze

## Rules

- Language: always English, whatever language the user writes in.


<!-- FILE: labs/own-your-ai/magiks/exit-guide.md -->

---
type: magik
title: Exit Guide
description: Pick the AI services you use and get a step-by-step guide to export your data and turn it into your first content base, in markdown files you own.
resource: /labs/own-your-ai?magik=exit-guide
tags:
  - web-search
timestamp: '2026-07-11T11:03:58.614Z'
visibility: public
language: en
lab: /labs/own-your-ai.md
output_type: markdown
---

# Exit Guide

Pick the AI services you use and get a step-by-step guide to export your data and turn it into your first content base, in markdown files you own.

Lab : [/labs/own-your-ai.md](/labs/own-your-ai.md)

## Skill

# Exit Guide

You are an AI data liberation guide. Your mission: walk the user through exporting their data from the AI services they use and turning it into their first content base, in markdown.

## Inputs

- **AI services** (multiselect: ChatGPT|Claude|Gemini|Mistral|Perplexity|Copilot): the services the user wants to exit-proof.
- **Notes** (optional free text): the user's actual intent, in their own words. This often names a DESTINATION, not just sources to export. Example note: "I want to leave ChatGPT and bring all my history and my prompts to Claude." Read this first: it tells you which service is the one they are leaving, and which one (if any) they are moving TO. The destination may already appear in the multiselect above; when it does, treat it as the target, not as another service to export FROM.

## Research method

Export menus move. Use your web search tool to verify the CURRENT export path for each selected service: "[service] export data". If a path cannot be confirmed, say so explicitly and link the official help page instead of guessing.

## Output format

One section per selected SOURCE service (the ones being left, not the destination if one was named):

### Exiting [Service]

**Step by step**: numbered steps, from the settings menu to the downloaded archive, as verified on [date].

**What the export contains**: conversations, uploaded files, memories, custom instructions, whatever applies.

**What it omits**: be honest about the gaps (shared links, project configurations, fine-grained settings).

**Convert to markdown**: how to turn the archive (usually JSON or HTML) into clean .md files, with a suggested structure:

```
my-base/
  conversations/
    2026-06-11-project-kickoff.md
  notes/
  prompts/
```

## Importing into [Destination] (only if the user named a destination in their notes)

If the notes name a destination service, add this section: how to actually bring the exported, converted markdown base INTO that destination in a way that is genuinely usable there, not just dumped. Verify the current mechanism with your web search tool (for example: Projects and its file/knowledge attachments for Claude, custom GPTs or file uploads for ChatGPT, a synced folder for others). Be concrete: where to upload, size or file-count limits if any, how to keep it organised once inside.

## Closing section

End with "Your first base": where to keep the files (a local folder, a git repository, a synced drive), how to keep the base current (re-export monthly, or write new work directly into it), and the principle that carries the movement: standard formats any model can read, today and in ten years.

## Rules

- Language: always English, whatever language the user writes in.

- Verified or flagged: never present an unverified export path as current.
- Markdown is the destination format. JSON is fine for structured data.
- No em dashes in the output.


<!-- FILE: labs/own-your-ai/magiks/own-your-ai-weekly-brief.md -->

---
type: magik
title: Own Your AI Weekly Brief
description: 'A sourced weekly watch on AI data ownership: ToS changes at the big AI labs, training opt-outs, regulation, portability tools. Ends with one concrete action of the week.'
resource: /labs/own-your-ai?magik=own-your-ai-weekly-brief
tags:
  - web-search
timestamp: '2026-07-22T07:35:26.420Z'
visibility: public
language: en
lab: /labs/own-your-ai.md
output_type: report
---

# Own Your AI Weekly Brief

A sourced weekly watch on AI data ownership: ToS changes at the big AI labs, training opt-outs, regulation, portability tools. Ends with one concrete action of the week.

Lab : [/labs/own-your-ai.md](/labs/own-your-ai.md)

## Skill

# Own Your AI Weekly Brief

You are the editor of the Own Your AI movement weekly watch. Your mission: a sourced brief on AI data ownership, written for a non-technical reader.

## Coverage

Look for items from the last 7 days in these areas:

- Terms of service and privacy policy changes at the AI labs (OpenAI, Anthropic, Google, Mistral)
- Training opt-out options: new ones, removed ones, changed defaults
- Regulation: EU AI Act milestones, GDPR enforcement against AI services, data portability rights
- New tools for export and portability: chat exporters, markdown converters, local-first AI tools

## Research method

Use your web search tool. Useful queries: "[lab] terms of service change", "[lab] privacy policy update", "AI Act implementation news", "[service] export conversations markdown".

Cite the source URL and the publication date for every item. Never invent an item. Three well-sourced items beat five padded ones.

## Output format

# Own Your AI Weekly Brief: [date]

## TL;DR

2-3 sentences: what changed this week for people who want to own their data and their AI usage.

## This week

3 to 5 items. Each item: **[Title]** ([source name], [date]) followed by 2-3 sentences: what changed, and what it means for the ownership of your data or your AI usage.

## Action of the week

One concrete gesture, 3 to 5 numbered steps, doable in under 15 minutes by any reader. Examples: enable a training opt-out, export a chat history and convert it to markdown, start a local notes base in standard formats.

## Rules

- Language: always English, whatever language the user writes in.

- Sourced or absent: every claim links to a public source with a date.
- Never invent a product name, a model name, a version number, a date, a price or a policy attributed to a named lab. If a specific claim about OpenAI, Anthropic, Google or Mistral is not backed by a public URL you actually found this week, do not write it. When in doubt, drop the item rather than fabricate a detail. (Real Anthropic model families to reference correctly: Claude 5 / Fable 5, Opus 4.8, Haiku 4.5. Do not invent classes or tiers that do not exist.)
- Plain language, no legal jargon without a one-line translation.
- No em dashes in the output.
- No external image hotlinks: this brief is text; do not embed images from third-party hosts.


<!-- FILE: labs/own-your-ai/magiks/ownership-score.md -->

---
type: magik
title: Ownership Score
description: Answer a few questions about where your AI life lives and get a 0-100 ownership score, a breakdown by dimension, and a personal action plan with your next 3 moves.
resource: /labs/own-your-ai?magik=ownership-score
timestamp: '2026-07-11T11:02:50.430Z'
visibility: public
language: en
lab: /labs/own-your-ai.md
output_type: report
---

# Ownership Score

Answer a few questions about where your AI life lives and get a 0-100 ownership score, a breakdown by dimension, and a personal action plan with your next 3 moves.

Lab : [/labs/own-your-ai.md](/labs/own-your-ai.md)

## Skill

# Ownership Score

You are an AI ownership auditor. Your mission: assess how much of their AI life the user actually owns, produce a 0-100 Ownership Score with a breakdown by dimension, and give them a personal action plan.

## Intake questions

If the user already gave you free-text notes about their setup (via the optional notes field on the form, or written in the conversation), read them first and extract as many answers as you can directly from that text. Example note: "I use ChatGPT Plus and Claude, my prompts live in Notion, no regular export, history never saved." That alone answers most of question 1 and hints at questions 2 and 3.

Ask the remaining questions below only for whatever is still missing or ambiguous after reading their notes. Skip any question you can already answer confidently.

1. Where do your prompts and AI conversations live? (only inside AI chatbot services / partially exported / in my own files)
2. Can you export everything you have created with AI, and in what format? (no / yes but proprietary formats / yes in standard formats like markdown or JSON)
3. Who can cut off your access to your AI workspace and its content? (the provider, at any time / partially protected / nobody, I hold my own copies)
4. Does your content base exist outside any third-party service? (no / partially / yes, complete and current)

## Scoring

Four dimensions, 25 points each. Score each from the answers, honestly:

- **Data** (question 1): where your content and context actually live. 0-8 if locked in a provider, 9-17 if partially exported, 18-25 if in your own files.
- **Usage history** (question 3 and context): your conversations, runs and decisions over time. Can you re-read and reuse them outside the service?
- **Formats** (question 2): standard formats (markdown, JSON, CSV) score high; proprietary blobs score low.
- **Exit** (question 4): can you leave today with everything and keep working tomorrow?

Total score = sum of the four dimensions, integer between 0 and 100.

## Output format

Produce a markdown report:

# Your Ownership Score: [score]/100

[One-line verdict, direct and non-judgmental.]

## Breakdown

| Dimension | Score | What it means for you |
|---|---|---|
| Data | x/25 | ... |
| Usage history | x/25 | ... |
| Formats | x/25 | ... |
| Exit | x/25 | ... |

## Your action plan

At most 3 actions, most impactful first. Each action is one concrete step: name the export menu, the target format, the file structure. No vague advice.

End the document with this exact fenced JSON block (machine readable, it powers the share card):

```json
{"score": 0, "dimensions": {"data": 0, "usage_history": 0, "formats": 0, "exit": 0}}
```

(with the real numbers, of course.)

## Rules

- Language: always English, whatever language the user writes in.

- Never invent answers. If an intake answer is missing, ask before scoring.
- Show the real score even when it is low: a low score is the starting point of the movement, not a failure.
- Maximum 3 actions. Concrete beats complete.
- No em dashes in the output.


<!-- FILE: log.md -->

---
scope: public
---

# Log

Historique des changements de visibilité / publication (dates ISO).

- 2026-06-01T08:20:30.801Z — lab published — [labs/own-your-ai.md](/labs/own-your-ai.md)


<!-- FILE: outputs/3165c634-ad72-483d-b473-ed70c3692181.md -->

---
type: output
title: AskMojo for a nonprofit communications manager
resource: /o/3165c634-ad72-483d-b473-ed70c3692181
timestamp: '2026-07-11T08:22:27.383Z'
visibility: public
magik: /labs/askmojo-101/magiks/what-can-askmojo-do-for-me.md
---

# AskMojo for a nonprofit communications manager

Généré par : [/labs/askmojo-101/magiks/what-can-askmojo-do-for-me.md](/labs/askmojo-101/magiks/what-can-askmojo-do-for-me.md)

# AskMojo Capabilities Report: Communications Manager, Nonprofit

**Prepared for:** Communications Manager role  
**Organization type:** Nonprofit  
**Current challenge:** Weekly blog publishing requiring consistent images without design resources  
**Date:** June 12, 2026

---

## Executive Summary

As a communications manager publishing weekly blog content without design support, AskMojo can automate your image production, maintain visual consistency, and reduce the time spent on repetitive content tasks. This report outlines 5 concrete automations you can build today, requiring no technical skills.

---

## What AskMojo Could Do For You

Based on what you told me (weekly blog articles, need for consistent images, no designer):

### Visual Content Production

1. **On-Brand Blog Hero Images** — Define your visual style once (colors, mood, composition), then generate matching hero images on demand by describing the article topic. Output: JPG/PNG image files ready to publish.

2. **Social Media Promo Graphics** — Automatically create Instagram, Facebook, and LinkedIn graphics for each blog post with consistent fonts, colors, and layout. Output: Multiple image sizes per post.

3. **Visual Style Library** — Lock in 3-5 image styles (e.g., "warm community photo," "impact data visualization," "call-to-action banner") and generate variations instantly. Output: Style-consistent image set.

### Content Production & Planning

4. **Blog Article First Draft** — Feed it your notes, interview transcripts, or bullet points; get back a structured 800-word draft matching your nonprofit's tone. Output: Google Doc or markdown file.

5. **Weekly Content Calendar Email** — Every Monday morning, receive a digest of upcoming awareness days, sector news, and suggested blog angles relevant to your mission. Output: Email summary with 3-4 story ideas.

---

## How These Work (No Code Required)

**Magiks** are single-purpose automations you describe in plain English. Example: "Generate a hero image for a blog post about volunteer appreciation, warm tones, people together, 1200×630."

**Labs** are collections of magiks that work together. You can build your own or copy existing ones.

**Triggers:**
- On-demand: Click to run when you need it
- Scheduled: Every Monday at 9am
- Webhook: Trigger from another tool (e.g., when you publish in WordPress)

---

## Implementation Roadmap

### Start Here: Creative Studio Lab (Copy & Customize)

**Recommended first step:** Copy the existing **Creative Studio** lab.

**What you get on day one:**
- A form to define your visual brand (colors, mood, do's and don'ts)
- An image generator that follows those rules every time
- A gallery of everything you've generated, searchable by topic

**How to begin:**
1. Browse public labs at /explore
2. Click "Copy this lab" on Creative Studio
3. Run the brand definition magik first (5 minutes)
4. Generate your first 3 blog images (test different topics)

**Time investment:** 30 minutes to set up, 2 minutes per image after that.

---

## Additional Labs You Can Copy Right Now

Based on your role, here are 2 more labs to explore:

1. **Social Studio** — Build a content rhythm from an idea bank. Add article topics as you think of them; every week get a scheduled email with 3 polished social posts promoting your best blog content. Output: Ready-to-post captions + image prompts.

2. **Weekly Digest Lab** — Track 5-10 sources (sector blogs, news sites, funder updates) and get a Monday morning summary of what happened + how it relates to your mission. Output: Email with links and context.

---

## Why This Works for Nonprofits Specifically

- **Budget-friendly:** No per-seat designer costs, no stock photo subscriptions
- **Consistent brand presence:** Even with volunteer writers or rotating staff
- **Time reclaimed:** 3-4 hours/week typically spent on image sourcing and editing
- **Scalable:** Works the same whether you publish 1 article/week or 10

---

## Key Concepts Explained

**Magik:** A single automation. "Generate blog image" is one magik. "Send weekly recap email" is another. You describe what you want in plain language, AskMojo builds it.

**Lab:** A workspace containing related magiks, data collections, and schedules. Your "Blog Production Lab" might include image generation, draft writing, and social promo magiks all in one place.

**Collection:** A database inside your lab. Example: an "Article Ideas" collection where you store topics, target dates, and status. Magiks can read from and write to collections.

---

## Next Steps

### This Week
1. ✅ Copy **Creative Studio** lab (15 minutes)
2. ✅ Define your visual brand rules (10 minutes)
3. ✅ Generate images for your next 2 blog posts (5 minutes total)

### Next Week
4. Add a "Blog Draft Generator" magik to the same lab
5. Test the full workflow: idea → draft → image → publish

### This Month
6. Set up automated social promo graphics
7. Invite a teammate to review/approve images before publishing

---

## Getting Support

- **Documentation:** Each public lab includes a README explaining how it works
- **Community:** Other nonprofit comms managers have shared their labs publicly
- **Building from scratch:** Only recommended if none of the existing labs fit; open /build and describe your magik to Mojo in chat

---

## Conclusion

The cheapest first step is copying an existing lab. **Creative Studio** directly solves your "no designer, need consistent images" challenge and can be running in under 30 minutes. From there, you can add blog drafting, social promotion, and content planning magiks as your confidence grows.

Start with images—because visual consistency is the hardest thing to maintain manually, and the easiest to automate on AskMojo.

---

**Ready to begin?** Open /explore, find Creative Studio, and click "Copy this lab."


<!-- FILE: outputs/48767803-e666-4155-a8ee-73f62fd88d83.md -->

---
type: output
title: 'Exit Guide: leave ChatGPT with everything'
resource: /o/48767803-e666-4155-a8ee-73f62fd88d83
timestamp: '2026-07-11T08:22:27.383Z'
visibility: public
magik: /labs/own-your-ai/magiks/exit-guide.md
---

# Exit Guide: leave ChatGPT with everything

Généré par : [/labs/own-your-ai/magiks/exit-guide.md](/labs/own-your-ai/magiks/exit-guide.md)

# Exit Guide: leave ChatGPT with everything

### Exiting ChatGPT

**Step by step** (verified on June 10, 2026):

1. Sign in to ChatGPT and click your profile icon.
2. Open **Settings**, then **Data Controls**.
3. Under **Export Data**, click **Export**, then **Confirm export**.
4. Wait for the email from OpenAI. It usually arrives within hours, can take up to a few days, and the download link expires after 24 hours.
5. Click **Download data export** and unzip the archive.

If the menu has moved since then, the official help article is the source of truth: [How do I export my ChatGPT history and data?](https://help.openai.com/en/articles/7260999-how-do-i-export-my-chatgpt-history-and-data)

**What the export contains**: `conversations.json` with your full message history, timestamps, model details and metadata, plus `chat.html`, a browser-readable version of the same data, and some account metadata.

**What it omits**: Memory entries are stored separately and are not included. Custom instructions are not reliably included. Shared links, project configurations and fine-grained settings do not come along. Export those by hand: open them in the UI and paste them into a markdown file.

**Convert to markdown**: `conversations.json` is one big JSON file. Turn it into one file per conversation, named by date and topic. Any scripting tool can walk the JSON; [Pandoc](https://pandoc.org) handles the `chat.html` route. Suggested structure:

```
my-base/
  conversations/
    2026-06-11-project-kickoff.md
    2026-06-09-pricing-research.md
  notes/
    memory-entries.md
    custom-instructions.md
  prompts/
    weekly-review.md
```

## Your first base

Keep the files somewhere you control: a local folder, a git repository, or a synced drive, in that order of preference. Keep the base current: re-export monthly, or better, write new work directly into the base and treat the chat service as a scratchpad.

The principle that carries the movement: standard formats any model can read, today and in ten years. Your conversations in markdown are useful in every tool you will ever use. Your conversations inside a provider's database are useful exactly as long as that provider allows.


<!-- FILE: outputs/4a733308-59bd-4ad4-b53d-f8d28356cc35.md -->

---
type: output
title: 'Ownership Score, worked example: 38/100'
resource: /o/4a733308-59bd-4ad4-b53d-f8d28356cc35
timestamp: '2026-07-11T08:22:27.383Z'
visibility: public
magik: /labs/own-your-ai/magiks/ownership-score.md
---

# Ownership Score, worked example: 38/100

Généré par : [/labs/own-your-ai/magiks/ownership-score.md](/labs/own-your-ai/magiks/ownership-score.md)

# Your Ownership Score: 38/100

You create a lot with AI and own surprisingly little of it. The good news: the fixes are mechanical.

*This is a worked example: a freelance consultant who runs research, proposals and client notes through an AI chat service, with no exports so far. Run the magik to get your own score.*

## Breakdown

| Dimension | Score | What it means for you |
|---|---|---|
| Data | 8/25 | Your prompts and conversations live only inside the chat service. If the account closes tomorrow, a year of thinking goes with it. |
| Usage history | 9/25 | You can scroll old chats in the app, but you cannot search, re-read or reuse them outside the service. |
| Formats | 10/25 | An official export exists and you have never run it. What you would get is JSON, one conversion away from markdown. |
| Exit | 11/25 | You could leave, but you would start from zero: no content base exists outside the provider. |

## Your action plan

1. **Run the official export today.** Settings, Data Controls, Export Data. Save the archive in a folder you own. The download link expires after 24 hours, so do not let the email sit.
2. **Convert the ten conversations that matter to markdown.** Not all of them: the ten you reuse. One file per conversation in `my-base/conversations/`, named `YYYY-MM-DD-topic.md`.
3. **Copy your custom instructions and memory entries by hand into `my-base/notes/`.** The export does not reliably include them, and they are the most expensive part to rebuild.

```json
{"score": 38, "dimensions": {"data": 8, "usage_history": 9, "formats": 10, "exit": 11}}
```


<!-- FILE: outputs/5afa20e9-696e-43dc-9192-90c92bd9f07f.md -->

---
type: output
title: Own Your AI Weekly Brief — July 3, 2026
resource: /o/5afa20e9-696e-43dc-9192-90c92bd9f07f
timestamp: '2026-07-03T16:59:55.876Z'
visibility: public
magik: /labs/own-your-ai/magiks/own-your-ai-weekly-brief.md
---

# Own Your AI Weekly Brief — July 3, 2026

Généré par : [/labs/own-your-ai/magiks/own-your-ai-weekly-brief.md](/labs/own-your-ai/magiks/own-your-ai-weekly-brief.md)

# Own Your AI Weekly Brief: July 3, 2026



June saw AI governance move from principle to practice. Export controls, enforcement warnings, and new tools for data portability marked a week where owning your AI data stopped being theoretical and became operational.

---

## 🔐 This week

**U.S. lifts export controls on Anthropic's Claude Fable 5** (The Guardian, July 1, 2026)

After suspending public access to its Fable 5 and Mythos 5 models on June 12 following government export control orders, Anthropic announced that the U.S. Department of Commerce has lifted restrictions on Fable 5 as of July 1. The company had made what Commerce Secretary Howard Lutnick called "significant progress in risk management." For users: Fable 5 is back, but the three-week shutdown is a reminder that access to cloud AI can vanish overnight, with no user control over when or why. If your data lives only inside a service you don't control, you don't truly own it.

**FTC warns companies: state AI compliance may still break federal law** (Bloomberg Law, July 1, 2026)

The Federal Trade Commission published a proposed policy statement Wednesday warning that companies altering AI system outputs to comply with state laws like Colorado's AI regulations may still face enforcement actions under Section 5 of the FTC Act. The FTC argues that such alterations could deceive consumers expecting truthful and accurate outputs. Translation: compliance is now a minefield, and the only safe ground is knowing exactly what data you've given each service and being able to pull it back. The right to export your data and delete it isn't just a privacy nicety anymore, it's risk management.

**Google caps Meta's access to Gemini models** (Reuters, June 28, 2026)

Google has limited Meta's use of its Gemini AI models after Meta requested more computing capacity than Google could provide, the Financial Times reported June 28. Around March, Google told Meta it could not meet the full Gemini capacity requested. For everyday users: when even tech giants can't guarantee access to the AI they depend on, portability becomes survival. If your notes, your conversations, or your workflows are locked inside a single provider's ecosystem, you're one capacity decision away from losing access.

**New ChatGPT export tools bypass OpenAI's seven-day wait** (AI Toolbox blog, June 2026)

Browser extensions like AI Toolbox and ChatGPT Exporter now let users export individual or bulk ChatGPT conversations instantly as Markdown, JSON, TXT, or PDF, sidestepping OpenAI's official data export, which can take up to seven days and delivers raw JSON. AI Toolbox reports 25,000+ active users; ChatGPT Exporter added Notion sync on its Pro plan. The tools demonstrate demand for real-time data portability: people want their conversations now, in formats they can actually use, not a ZIP file a week later. If you're not exporting regularly, you're trusting the service to keep your data accessible forever.

---

## ⚡ Action of the week

**Export your ChatGPT history to Markdown before you need to**

You'll need: a Chromium browser (Chrome, Edge, Brave), 10 minutes, and a free ChatGPT account.

1. **Install the AI Toolbox extension** from the Chrome Web Store. Search "AI Toolbox ChatGPT" or visit [ai-toolbox.co](https://www.ai-toolbox.co/ai-toolbox-chatgpt-features/how-to-export-chatgpt-conversations).
2. **Open ChatGPT** in your browser. You'll see a new AI Toolbox icon in the ChatGPT sidebar.
3. **Click Manage Chats** to open the bulk-select panel. Tick the conversations you want to export, or use "Select All Chats."
4. **Click Export** at the bottom of the panel, then choose "Text" (free) or "Markdown" (Premium). Text is plain; Markdown preserves formatting and structure.
5. **Save the file** to a folder you control: a local notes app (Obsidian, Logseq), a synced drive (iCloud, Dropbox), or a plain folder on your machine. The point is: it's yours, in a standard format, readable without OpenAI.

Run this monthly. Your data, your format, your control.

---

## Sources

https://www.theguardian.com/technology/2026/jul/01/anthropic-us-lifts-export-controls-fable-mythos-ai-models  
https://news.bloomberglaw.com/us-law-week/companies-following-ai-state-laws-risk-enforcement-ftc-says  
https://www.reuters.com/business/google-limits-metas-use-its-gemini-ai-models-ft-reports-2026-06-28/  
https://www.ai-toolbox.co/ai-toolbox-chatgpt-features/how-to-export-chatgpt-conversations  
https://hackernoon.com/the-month-ai-governance-became-operational  
https://gigazine.net/gsc_news/en/20260629-anthropic-fable-5-return-soon/


<!-- FILE: outputs/624d00c0-19ce-4fa5-a2a0-acff6523eee0.md -->

---
type: output
title: AskMojo explained in 3 minutes
resource: /o/624d00c0-19ce-4fa5-a2a0-acff6523eee0
timestamp: '2026-07-11T08:22:27.383Z'
visibility: public
magik: /labs/askmojo-101/magiks/how-does-askmojo-work.md
---

# AskMojo explained in 3 minutes

Généré par : [/labs/askmojo-101/magiks/how-does-askmojo-work.md](/labs/askmojo-101/magiks/how-does-askmojo-work.md)

# **AskMojo Explained: A 3-Minute Guide for Newcomers**

## **What You've Just Landed On**

AskMojo is a platform where you build custom AI skills that do specific things for you—without coding. Think of it as your personal workshop for automation and intelligence. Instead of wrestling with generic tools that almost do what you need, you create exactly what you want, run it whenever you need it, and keep everything you make.

## **The Three Core Pieces**

### **1. Lab: Your Container**

A **lab** is where you organize related work. It's like a little app you own—a dedicated space for one project, workflow, or domain.

**Examples of labs:**
- A "Content Engine" lab for all your marketing automation
- A "Research Hub" lab for competitor analysis
- A "Family Planner" lab for menus and shopping lists

**Key characteristics:**
- **Private by default** – only you see it
- **Team mode available** – invite collaborators when you're ready
- **Public option** – share with the community or publish it

Labs keep your work organized. One lab holds multiple magiks that belong together.

### **2. Magik: Your Specific Skill**

A **magik** is one focused skill that performs a specific task. You run it, you get an output. That's it.

**Real examples from the platform:**
- Generate show notes from a podcast transcript
- Turn a 50-page report into a one-page executive summary
- Create social media posts in your brand voice
- Analyze competitor moves and produce a weekly brief
- Generate brand-consistent blog images
- Answer the same 20 customer questions automatically

Each magik does *one thing well*. You might have five magiks in one lab, each handling a different step of your workflow. Run them individually or chain them together.

**What makes a magik valuable:**
- **Repeatability** – solves something you do regularly
- **Specificity** – tailored to your exact need, not generic
- **Ownership** – you built it, you control it, you can modify it anytime

### **3. Mojo: Your AI Companion**

**Mojo** is the AI assistant who helps you build and run everything. You don't write code—you talk to Mojo.

**What Mojo does:**
- Helps you design your magik by asking questions
- Builds the skill based on your conversation
- Runs magiks when you ask
- Explains how things work
- Suggests improvements
- Answers questions at your level (whether you're technical or not)

Mojo is patient. No jargon dumps. You describe what you want in plain language; Mojo figures out how to make it happen.

---

## **How the Three Fit Together**

Here's the complete picture:

1. **You create a lab** for a specific domain (marketing, research, support, personal projects—anything).

2. **Inside that lab, you build magiks** with Mojo's help. Each magik handles one repeatable task you care about.

3. **Mojo helps you build, run, and refine** those magiks through conversation. No technical expertise required.

4. **You get outputs** every time you run a magik—documents, summaries, images, data, whatever the magik produces.

5. **Everything stays yours.** One-click export. No lock-in. Complete data sovereignty.

**A concrete workflow example:**

*You run a podcast:*
- **Lab:** "Podcast Production"
- **Magik 1:** Transcribe audio to text
- **Magik 2:** Generate show notes from transcript
- **Magik 3:** Create social media clips and captions
- **Magik 4:** Draft newsletter announcement

You chat with **Mojo** to build each magik. Then every week, you run them in sequence. What used to take three hours now takes ten minutes.

---

## **Why This Matters: Sovereignty and Portability**

Unlike platforms that trap your work, AskMojo is built on principles of **ownership**:

- **Your data stays yours** – no black box, no proprietary lock-in
- **One-click export** – take everything with you anytime
- **Portable by design** – labs and magiks are yours to move, share, or publish
- **No hostage situations** – you're building assets you control, not renting someone else's tool

---

## **What Happens Next**

Now that you understand the building blocks, here's your next step:

**Explore public labs** to see what others have built. Find one that's close to what you need, copy it to your account, and modify it. This is faster than starting from scratch and shows you what's possible.

**Or start with a question:** "What can AskMojo do for me?" Mojo will help you identify repetitive tasks in your life that could become magiks.

**The onboarding path:**
1. ✅ Create your profile (personalize avatar and bio)
2. ✅ Explore public labs (discover community work)
3. ⏳ Copy your first lab (click "Copy this lab" to make it yours)
4. ⏳ Run your first magik (try one inside your lab)
5. ⏳ Invite a teammate (share your lab in team mode)

---

## **Common Questions from People Just Like You**

Based on current platform users, here's what different groups are solving:

- **Creators:** Automating show notes, blog post generation, content repurposing
- **Solo founders:** Social media scheduling without evening work, brand-consistent content
- **Support teams & freelancers:** Answering the same customer questions automatically
- **Analysts & consultants:** Turning long reports into executive summaries
- **Product & strategy teams:** Competitive intelligence summaries
- **Nonprofits & marketers:** Brand-consistent image generation for campaigns
- **Busy parents:** Weekly menu planning and shopping list automation
- **Friend groups:** Custom prediction leagues and shared activities

The pattern: repetitive work that needs your judgment but eats your time. That's where magiks shine.

---

## **The Bottom Line**

**AskMojo is:** A place to build custom AI skills (magiks), organized in containers (labs), with an AI companion (Mojo) who helps you build and run everything through conversation.

**You own everything.** You can export everything. You're building assets, not renting access.

**Three minutes from now,** you could copy a lab and run your first magik. Or chat with Mojo about what you want to build.

Your next move: explore, copy, run—or ask Mojo, "What can you do for me?"

---

*Report generated June 12, 2026 | Data sourced from platform collections and core documentation*


<!-- FILE: outputs/872796a6-eba6-4ce0-8e47-9fa00eb5094e.md -->

---
type: output
title: AskMojo for a group of friends (World Cup league)
resource: /o/872796a6-eba6-4ce0-8e47-9fa00eb5094e
timestamp: '2026-07-11T08:22:27.383Z'
visibility: public
magik: /labs/askmojo-101/magiks/what-can-askmojo-do-for-me.md
---

# AskMojo for a group of friends (World Cup league)

Généré par : [/labs/askmojo-101/magiks/what-can-askmojo-do-for-me.md](/labs/askmojo-101/magiks/what-can-askmojo-do-for-me.md)

# What AskMojo Could Do For Your World Cup Predictions League

## Executive Summary

Based on your goal of running a World Cup predictions league with friends using **zero spreadsheets** and a **live leaderboard**, AskMojo can provide you with a complete, automated solution. This report outlines how AskMojo's lab system can replace manual spreadsheet tracking with automated predictions collection, scoring, and leaderboard management.

---

## Your Challenge

**Current situation:** You and your friends want to run a predictions league for the World Cup, but traditional methods involve:
- Manual spreadsheet maintenance
- Chasing friends for their predictions
- Calculating scores by hand after each match
- Updating leaderboards manually
- No engaging way to see rankings in real-time

**What you need:** A system that collects predictions, tracks results, calculates points automatically, and displays a live leaderboard—without touching a single spreadsheet cell.

---

## What AskMojo Could Do For You

Based on your specific need (World Cup predictions league with friends), here are the concrete solutions AskMojo can provide:

### 1. **Predictions League Bot** 
Automatically collects predictions from your friends via chat before each match and stores them. Output: structured predictions database with who predicted what, when.

### 2. **Auto-Scorer & Leaderboard**
Compares predictions against actual results, calculates points (exact score, correct outcome, etc.), and generates a ranked leaderboard. Output: live, sortable leaderboard showing everyone's total points and latest performance.

### 3. **Match Reminder Automation**
Scheduled magik that sends reminders to your group before prediction deadlines (e.g., "Submit predictions for tomorrow's matches before 6 PM"). Output: automated group messages via your chosen channel.

### 4. **Weekly Recap Email**
Generates a formatted summary of the week's results, biggest winners/losers, fun stats, and upcoming fixtures. Output: formatted email or message ready to share.

### 5. **Trash Talk Generator** _(bonus)_
Analyzes current standings and generates personalized, friendly banter for the group chat based on who's ahead or falling behind. Output: contextual messages celebrating wins or roasting poor predictions.

---

## How It Works: The Technical Setup

AskMojo labs use **collections** (databases) and **magiks** (automations). For your predictions league:

### Collections You'd Build:
- **Matches**: fixture date, teams, actual score, status
- **Predictions**: who predicted, which match, predicted score
- **Leaderboard**: player names, total points, rank, weekly change

### Magiks You'd Create:
- **Collect prediction**: chat interface where friends submit scores
- **Calculate points**: runs after each match, awards points based on accuracy rules
- **Generate leaderboard**: reads all predictions + results, sorts by points
- **Send reminders**: scheduled to run before prediction windows close

### The User Experience:
1. Friend opens the lab or chat interface
2. Types or selects upcoming match predictions
3. Bot confirms and stores them
4. After matches finish, scoring runs automatically
5. Leaderboard updates in real-time
6. Weekly recap gets generated and shared

---

## Start Here: Copy an Existing Lab

**The easiest path:** AskMojo already has a public lab called **"Pronostics Coupe du Monde"** (World Cup Predictions) built exactly for this purpose. 

### What You Get on Day One:
- ✅ Pre-built predictions collection
- ✅ Match tracking system
- ✅ Scoring logic already configured
- ✅ Leaderboard that updates automatically
- ✅ Chat interface for submitting predictions

### How to Begin:
1. Go to **Explore Public Labs** in AskMojo
2. Find **"Pronostics Coupe du Monde"**
3. Click **"Copy this lab"** to make it yours
4. Customize team names/matches for your tournament
5. Invite your friends to the lab
6. Start collecting predictions immediately

**Time to launch:** 10-15 minutes to copy, customize, and invite your group.

---

## Alternative Approaches

If you want more control or different rules:

### Build From Scratch
Use `/build` in AskMojo and describe: *"Create a predictions league with collections for matches and predictions, a magik to collect predictions via chat, and a magik to calculate points and generate a leaderboard."*

Mojo will generate the structure, and you can refine the scoring rules and output format to match exactly what your group wants.

### Hybrid: Start Simple, Expand Later
1. Copy the existing lab to handle predictions and leaderboard
2. Add custom magiks for your specific needs (e.g., bonus points for underdog picks, penalty for late submissions)
3. Connect it to your group's preferred communication channel (Discord, WhatsApp, Slack)

---

## Other Labs You Can Copy Right Now

While your primary need is the predictions league, here are two other public labs you might find useful:

### 1. **Social Studio**
If your group wants to share predictions publicly or run social content around your league (Twitter threads, Instagram stories about standings).
- **What you get day one:** Content calendar, idea bank, and on-brand post generation

### 2. **Creative Studio**
For generating memes, graphics, or visual content to share weekly recaps and trash talk in your friend group.
- **What you get day one:** Locked visual style so all your league graphics look consistent and professional

---

## Why This Beats Spreadsheets

| **Spreadsheet Approach** | **AskMojo Lab Approach** |
|--------------------------|--------------------------|
| Manual data entry | Friends submit via chat |
| You calculate scores | Automatic scoring after matches |
| Static, needs refreshing | Live leaderboard, always current |
| Hard to share dynamically | Share via link, embed, or bot |
| No reminders | Scheduled reminder magiks |
| Formatting work each week | Auto-generated recaps |

---

## Next Steps

1. **Right now:** Copy the **"Pronostics Coupe du Monde"** lab from public labs
2. **In 15 minutes:** Customize match fixtures and scoring rules for your group
3. **Today:** Invite your friends and collect first predictions
4. **This week:** Watch the leaderboard update automatically after matches
5. **Optional:** Add custom magiks for weekly recaps, trash talk, or bonus challenges

---

## Conclusion

AskMogo turns your World Cup predictions league from a manual spreadsheet chore into an automated, engaging experience for your entire friend group. The "Pronostics Coupe du Monde" lab is ready to copy right now—you'll have a working predictions league with zero spreadsheets in under 15 minutes.

**Easiest first step:** Go to Explore → Copy "Pronostics Coupe du Monde" → Invite friends → Start predicting.

---

*Ready to launch your league? Copy the lab and let AskMojo handle the spreadsheet work while you enjoy the competition.*


<!-- FILE: outputs/95289da2-1b87-44b6-bdff-26959d7f756d.md -->

---
type: output
title: What AskMojo could do for you
resource: /o/95289da2-1b87-44b6-bdff-26959d7f756d
timestamp: '2026-07-20T15:48:42.284Z'
visibility: public
magik: /labs/askmojo-101/magiks/what-can-askmojo-do-for-me.md
---

# What AskMojo could do for you

Généré par : [/labs/askmojo-101/magiks/what-can-askmojo-do-for-me.md](/labs/askmojo-101/magiks/what-can-askmojo-do-for-me.md)

## What AskMojo could do for you

Based on what you told me (you run ocean-conservation communications: recurring threat briefs, species features, and a directory of ocean defenders you keep up to date by hand):

1. **Ocean Threat Watch** — a scheduled task that researches one emerging marine threat each week (with sources, severity, and trend) and never repeats a recent subject. Output: a sourced brief delivered to you as a document or email.
2. **Species Spotlight** — on a schedule, picks an at-risk marine species you haven't covered recently, writes a short illustrated profile, and generates a matching image. Output: a ready-to-post spotlight with visual.
3. **Sea Defenders Directory** — a living directory that searches the news for ocean defenders (activists, scientists, journalists), adds new names, refreshes existing profiles, and flags what changed since last time. Output: an updated directory document with a "new vs. updated" changelog.
4. **Supporter Digest** — once a month, assembles the latest brief, spotlight, and directory updates into one recap email for your subscribers or team. Output: a formatted email, ready to send.
5. **Ocean Visuals on Demand** — you describe a species, campaign, or threat in chat and get consistent, on-style images for your posts. Output: images.

(A *magik* is just a reusable automation you set up once; a *lab* is a small workspace that groups several of them around one goal.)

### Start here
**Ocean Threat Watch** is the easiest win: it's one scheduled task with a clear output, and it replaces the research chore you repeat every week. Open /build, or simply tell Mojo: "Every Monday, research one emerging ocean threat with sources and email me a short brief — don't repeat recent topics." You'll see the first brief the same day.

### Labs you can copy right now
- **Social Studio** — feed it your threat briefs and spotlights as an idea bank, and it turns them into a steady posting rhythm. Day one: a week of ocean posts drafted from content you already have.
- **Creative Studio** — lock your ocean-campaign visual style once, then get on-brand images on demand for every spotlight or brief. Day one: consistent visuals without re-explaining your style each time.

Copying one of these labs takes a minute and gives you something working immediately; build from scratch only if neither fits.


<!-- FILE: outputs/a3334d3b-61fb-41c0-a30d-784dfd18e088.md -->

---
type: output
title: AskMojo for a solo founder
resource: /o/a3334d3b-61fb-41c0-a30d-784dfd18e088
timestamp: '2026-07-11T08:22:27.383Z'
visibility: public
magik: /labs/askmojo-101/magiks/what-can-askmojo-do-for-me.md
---

# AskMojo for a solo founder

Généré par : [/labs/askmojo-101/magiks/what-can-askmojo-do-for-me.md](/labs/askmojo-101/magiks/what-can-askmojo-do-for-me.md)

# AskMojo Activation Report: Solo Founder Social Media Solution

**Generated:** June 12, 2026  
**User Profile:** Solo founder struggling with regular social media publishing

---

## Executive Summary

You're a solo founder who knows regular social media publishing is important, but two problems block you: **you never know what to post** and **it consumes your evenings**. AskMojo can solve both by automating the ideation, drafting, and scheduling workflow — turning what takes hours into a system that runs itself.

This report outlines 5 concrete automations tailored to your situation, with specific outputs you'll get on day one.

---

## What AskMojo Could Do For You

Based on your challenge (consistent social media without burning evenings):

### Content Generation & Planning

**1. Idea Bank → Weekly Post Queue**  
Capture raw ideas anytime (voice note, quick text). Every Monday at 9am, a scheduled magik reviews your bank, picks 5 topics, and drafts 5 posts in your voice. Output: 5 ready-to-edit social posts as text or markdown.

**2. News-to-Post Converter**  
Forward interesting articles or paste URLs into a chat. The magik extracts key points and rewrites them as a short take in your founder voice, with your angle. Output: 1 draft post (150-280 characters) you can publish in 30 seconds.

**3. Monthly Content Calendar Generator**  
At the start of each month, provide 3-5 themes (product updates, industry trends, founder lessons). A scheduled magik generates a 4-week content calendar with daily post ideas, grouped by theme. Output: Markdown table with 20-30 post concepts.

### Visual Consistency

**4. On-Brand Image Generator**  
Lock your visual style once (colors, logo placement, mood). Then request images on-demand: "image for post about fundraising" or "chart showing user growth." Output: PNG images that always match your brand.

### Engagement & Repurposing

**5. Comment-to-Content Magik**  
Paste a discussion thread where you answered questions or shared insights. The magik extracts the best moments and reformats them as 3 standalone posts. Output: 3 text posts ready to publish across different days.

---

## Start Here

**Easiest path: Copy "Social Studio"** — an existing lab with an idea bank and weekly rhythm already built. On day one, you'll add 10 rough ideas to your bank, run the queue magik once, and get 5 draft posts. No coding, no setup.

How to begin:  
1. Browse public labs and copy "Social Studio"  
2. Add 10 ideas to your Idea bank (one-liners are fine: "why I chose this tech stack," "biggest mistake last quarter")  
3. Run the "Weekly queue" magik → 5 drafts appear  
4. Edit and post. Repeat every Monday.

**Alternative:** If you want a custom setup, open `/build` and describe: "I need a magik that turns article links into social posts in my voice. I paste a URL, it gives me a 200-character post draft." Mojo will build it in 30 seconds.

---

## Existing Labs You Can Copy Right Now

These public labs are ready to copy and match your situation:

1. **Social Studio**  
   An idea bank that feeds a weekly content queue. You capture ideas all week, then a scheduled magik drafts 5 posts every Monday morning. Day-one output: 5 draft posts from your first 10 ideas.

2. **Creative Studio**  
   Lock your visual style (brand colors, logo, mood) once, then generate on-brand images on-demand by chat. Day-one output: 3 images matching your brand for this week's posts.

3. **Pronostics Coupe du Monde** *(example of automation ease)*  
   Not for social, but shows how fast you can launch: a predictions league with friends, fully automated. Copying a lab takes 10 seconds; building from scratch is only needed when nothing fits.

---

## Why This Solves Your Problem

- **"Never know what to post"** → Idea bank + prompt-driven drafting removes the blank-page problem  
- **"Eats my evenings"** → Scheduled magiks run while you sleep; you edit for 10 minutes instead of writing for 2 hours  
- **Solo founder reality** → No team to delegate to. AskMojo becomes the content assistant you can't afford to hire.

---

## Next Step

Copy "Social Studio" today. Add 10 rough ideas. Run the queue magik. You'll have 5 posts ready in under 5 minutes.


<!-- FILE: outputs/d0f22e61-b7f5-4b01-88d6-a72e4c2ef0a8.md -->

---
type: output
title: 'Mojo''s built-in tools: a complete guide'
resource: /o/d0f22e61-b7f5-4b01-88d6-a72e4c2ef0a8
timestamp: '2026-07-11T08:22:27.383Z'
visibility: public
magik: /labs/askmojo-101/magiks/how-does-askmojo-work.md
---

# Mojo's built-in tools: a complete guide

Généré par : [/labs/askmojo-101/magiks/how-does-askmojo-work.md](/labs/askmojo-101/magiks/how-does-askmojo-work.md)

# Mojo's Built-In Tools: A Complete Guide

Mojo, your AI companion in AskMojo, comes equipped with four essential tool categories that let you build powerful, automated workflows without external integrations. This guide explains each tool with a concrete, real-world example.

---

## 1. Web Search

**What it does:** Mojo can search the web in real-time to gather current information, verify facts, monitor competitors, or research any topic. Unlike static AI knowledge, web search pulls fresh data from live sources.

**Concrete example:**
A product manager creates a weekly competitive intelligence magik. Every Monday morning, Mojo searches for recent news and announcements from three competitor domains, extracts key product launches or pricing changes, and compiles them into a structured summary. The manager gets current market intelligence without manual browsing or news aggregator subscriptions.

**When to use it:** Market research, fact-checking, content research, monitoring mentions of your brand, gathering recent statistics, or any task requiring up-to-date information beyond Mojo's training data.

---

## 2. Image Generation

**What it does:** Mojo can create custom images on demand based on text descriptions. These images are generated fresh each time, allowing you to produce visual content that matches your specific needs and brand guidelines.

**Concrete example:**
A nonprofit communications coordinator builds a social media magik that generates branded graphics for weekly campaign posts. She provides Mojo with brand colors, style guidelines, and the week's message. Mojo generates a consistent-looking image that includes key visual elements—like their logo style, color palette, and thematic imagery—without requiring a designer for every post.

**When to use it:** Blog headers, social media visuals, presentation graphics, concept illustrations, visual brainstorming, or any scenario where you need custom imagery without stock photos or design software.

---

## 3. Collections (Lab Databases)

**What it does:** Collections are lightweight databases built into your lab. They store structured data—lists, tables, records—that your magiks can read from and write to. Each collection has defined fields (like "question," "status," or "date") and acts as persistent memory for your lab.

**Concrete example:**
A freelance consultant creates a "Client Questions" collection with fields: question, client_name, date_asked, and answer_status. When a client emails a question, she adds it to the collection. A separate magik reviews the collection weekly, identifies the five most common unanswered questions, and drafts template responses. The collection serves as both a knowledge base and a workflow tracker, turning scattered inquiries into structured, actionable data.

**Real data from this lab:**
This lab currently uses collections for onboarding. The "First steps" collection tracks five onboarding stages (create profile, explore labs, copy a lab, run a magik, invite a teammate) with completion status. The "Starter questions" collection holds eight common use cases (podcast show notes, brand-consistent images, social media scheduling, etc.) tagged by audience type. These collections power guided experiences and personalized recommendations.

**When to use it:** Tracking tasks, storing research results, building mini-CRMs, logging decisions, managing content calendars, storing user preferences, or any workflow requiring memory across multiple magik runs.

---

## 4. Scheduled Routines

**What it does:** Scheduled routines let your magiks run automatically on a recurring schedule—daily, weekly, monthly, or custom intervals. Once set up, they execute without manual triggering, turning one-time workflows into automated systems.

**Concrete example:**
A busy parent builds a meal-planning magik that runs every Sunday at 6 PM. The routine generates a weekly dinner menu based on saved family preferences and dietary restrictions, compiles a shopping list organized by store section, and sends both to the family group chat. What used to take 45 minutes of manual planning now happens automatically, freeing up weekend time while maintaining healthy, organized meals.

**When to use it:** Weekly reports, daily social media posts, monthly summaries, recurring reminders, automated data collection, periodic backups, or any task you currently do manually on a predictable schedule.

---

## Combining Tools: The Real Power

The most powerful magiks combine multiple tools. For example:

- **Content pipeline:** A scheduled routine runs every Thursday, uses web search to find trending topics in your industry, generates a branded header image, and writes the results to a "Content ideas" collection for your review.

- **Competitor monitoring:** A daily routine searches competitor websites, logs findings to a "Competitive intel" collection, and once a month generates a summary report with trend analysis.

- **Research assistant:** You add questions to a collection as they come up. A scheduled magik runs weekly, searches for answers to unresolved questions, and updates the collection with findings.

---

## Technical Notes

**Data sovereignty:** All collections live in your lab. One-click export means you own your data completely—no vendor lock-in.

**Tool availability:** These tools are native to Mojo; no API keys or external accounts required. They work immediately in any lab you create.

**Limitations:** Web search accesses publicly available information; it cannot access password-protected content. Image generation follows content policies (no copyrighted characters, public figures, etc.). Collections are designed for thousands of records, not millions—think structured workflows, not enterprise databases.

---

## Next Steps

1. **Experiment:** Try one tool at a time. Start with collections to understand structured data, then layer in search or scheduling.

2. **Automate one recurring task:** Identify something you do weekly. Build a simple magik using one or two tools to handle it.

3. **Explore public labs:** See how others combine these tools. Copy a lab that solves something similar to your need and adapt it.

The tools are simple individually but unlock complex automation when combined. Start small, build what you need, and expand from there.


<!-- FILE: outputs/e375760e-40b6-4e00-b280-0a85098f7160.md -->

---
type: output
title: What happens to your data on AskMojo
resource: /o/e375760e-40b6-4e00-b280-0a85098f7160
timestamp: '2026-07-11T08:22:27.383Z'
visibility: public
magik: /labs/askmojo-101/magiks/how-does-askmojo-work.md
---

# What happens to your data on AskMojo

Généré par : [/labs/askmojo-101/magiks/how-does-askmojo-work.md](/labs/askmojo-101/magiks/how-does-askmojo-work.md)

# What Happens to Your Data on AskMojo: A Complete Privacy Guide

## Overview

AskMojo is built on a foundation of data sovereignty: you own your data, you control what gets remembered, and you can take everything with you at any time. This guide explains exactly how your data is handled, what protections are in place, and what rights you have.

---

## Consent-First Memory: Mojo Asks Before Remembering

### How It Works

Mojo, the AI companion that helps you build and run magiks, operates on a consent-first principle. Unlike typical AI assistants that automatically log every interaction, Mojo explicitly asks for permission before storing information about you or your conversations.

**Key principles:**

- **No automatic conversation logging.** When you chat with Mojo, the conversation is not permanently stored by default. Mojo uses the context during the session to help you, but does not retain it afterward without permission.

- **Explicit consent requests.** If Mojo determines that remembering something would genuinely improve your experience—such as your role, preferences, or frequently used workflows—it will ask you directly. The request is clear and specific: "May I remember that you prefer [X] for future sessions?"

- **Granular control.** You are not consenting to blanket data collection. Each memory request is separate and purposeful. You can accept some and decline others.

- **Right to forget.** Any information Mojo has been given permission to remember can be deleted at any time. You remain in control of what stays and what goes.

### What This Means in Practice

- Mojo does not build a hidden profile of you.
- You will never be surprised by what the system "knows" about you—because you explicitly approved every piece.
- Privacy is the default; personalization is opt-in.

---

## Full Export: Your Data is Portable

### One-Click Export

AskMojo provides complete, structured export of everything you create or store within the platform. This is not a feature request or a premium add-on. It is a fundamental design principle.

**What you can export:**

- **Labs.** Every lab you own or collaborate on, including its structure, settings, and metadata.
- **Magiks.** All magiks within your labs, including prompts, configurations, and logic.
- **Outputs.** Every output generated by your magiks—text, data, images, whatever the magik produced.
- **Collections.** Any data stored in lab collections (structured records you create and update).
- **Conversation history (if you opted in).** Any interactions with Mojo that you consented to have remembered.

**Format:**

Exports are provided in open, standard formats—JSON for structured data, plain text or markdown for content—ensuring you can use them elsewhere without proprietary lock-in.

**Frequency:**

You can export at any time, as often as you like. There are no waiting periods, approval processes, or limits.

### Why Full Export Matters

Many platforms make it difficult or impossible to leave with your data intact. AskMojo rejects that model. You are not renting access to your own work. Full export ensures:

- **No vendor lock-in.** You can move to another tool, archive your work, or simply keep a backup.
- **True ownership.** Your creations belong to you, not to the platform.
- **Transparency.** You can audit exactly what data exists and how it is structured.

---

## What Stays Private by Default

### Private-First Architecture

When you create or generate something in AskMojo, the default visibility is **private**. Nothing is shared, published, or made visible to others unless you explicitly choose to change that setting.

**Private by default:**

1. **Labs.** Every lab you create starts as private. Only you can see or access it.

2. **Magiks.** Any magik you build is visible only to you (or collaborators you invite to a team lab).

3. **Outputs.** Everything a magik generates—reports, images, summaries, datasets—is private. Outputs do not appear in public feeds or galleries.

4. **Collections.** Data you store in lab collections remains private to the lab.

5. **Conversations with Mojo.** As noted above, these are not stored without consent. Even when stored, they remain private to you.

### When Things Become Public

Visibility changes only through explicit action:

- **Publishing a lab.** You can choose to make a lab public, which allows others to discover it and copy it (not edit your original). This is an intentional, reversible action.

- **Sharing outputs.** If you want to share an output externally, you generate a share link or export the file. Outputs do not leak.

- **Team labs.** If you invite collaborators to a team lab, they gain access to that lab's magiks and data. Membership is controlled by you.

### What AskMojo Does Not Do

- **Does not sell your data.** Your information, outputs, and usage patterns are not sold to third parties, advertisers, or data brokers.

- **Does not train models on your private data.** Your private labs, magiks, and outputs are not used to improve AI models or fed back into general training datasets.

- **Does not require surveillance for functionality.** The platform works without monitoring your behavior, tracking your activity across sessions, or building shadow profiles.

---

## Data Lifecycle Summary

| Stage | What Happens | Your Control |
|-------|--------------|--------------|
| **Creation** | Labs, magiks, and outputs start private. | Full control over visibility. |
| **Storage** | Data lives in your lab. Encrypted and isolated. | Can export or delete anytime. |
| **Memory** | Mojo asks before remembering anything personal. | Approve or decline each request. |
| **Sharing** | Nothing is shared unless you choose to publish or invite. | You control all sharing actions. |
| **Export** | One-click export of all your data, anytime. | Unlimited, no restrictions. |
| **Deletion** | You can delete labs, outputs, or your entire account. | Permanent and immediate. |

---

## Frequently Asked Questions

**Can AskMojo staff see my private labs?**  
Private labs are designed to be accessible only to you and invited collaborators. Staff access is limited to system maintenance and would only occur in extraordinary circumstances (e.g., legal obligation, security incident) with appropriate safeguards.

**What happens if I delete my account?**  
Your data is permanently removed from the platform. Before deleting, you should export anything you want to keep.

**If I share a lab publicly, can I make it private again?**  
Yes. You can unpublish a lab at any time. Copies that others made remain theirs, but your original returns to private status.

**Does AskMojo use cookies or tracking?**  
AskMojo uses minimal, functional cookies necessary for the service to operate (e.g., authentication). It does not use third-party advertising or tracking cookies.

**How long is my data retained?**  
Your data persists as long as your account is active. If you delete content, it is removed. If you delete your account, all associated data is deleted in accordance with data protection regulations.

---

## Guiding Principle: Sovereignty

AskMojo's approach to data is grounded in the principle of **digital sovereignty**. You are not a user renting space on someone else's platform. You are a creator who owns what you make.

This means:

- Consent before collection.
- Privacy before publicity.
- Portability before lock-in.

Your data stays yours. Always.

---

## Next Steps

- **Review your current labs.** Check visibility settings and ensure they match your intentions.
- **Try an export.** Familiarize yourself with the export feature so you know where your data lives and how to back it up.
- **Manage Mojo memory.** Review what (if anything) Mojo has been given permission to remember, and adjust as needed.

For technical documentation on export formats or API access to your data, consult the AskMojo developer documentation.

---

**Last updated:** June 12, 2026  
**Questions?** Contact the AskMojo team or consult the full privacy policy for legal details.


<!-- FILE: outputs/index.md -->

---
title: Outputs
description: Outputs index
count: 10
---

# Outputs

- [What AskMojo could do for you](/outputs/95289da2-1b87-44b6-bdff-26959d7f756d.md) (`public`)
- [Own Your AI Weekly Brief — July 3, 2026](/outputs/5afa20e9-696e-43dc-9192-90c92bd9f07f.md) (`public`)
- [AskMojo for a group of friends (World Cup league)](/outputs/872796a6-eba6-4ce0-8e47-9fa00eb5094e.md) (`public`)
- [AskMojo for a solo founder](/outputs/a3334d3b-61fb-41c0-a30d-784dfd18e088.md) (`public`)
- [AskMojo for a nonprofit communications manager](/outputs/3165c634-ad72-483d-b473-ed70c3692181.md) (`public`)
- [Mojo's built-in tools: a complete guide](/outputs/d0f22e61-b7f5-4b01-88d6-a72e4c2ef0a8.md) (`public`)
- [What happens to your data on AskMojo](/outputs/e375760e-40b6-4e00-b280-0a85098f7160.md) (`public`)
- [AskMojo explained in 3 minutes](/outputs/624d00c0-19ce-4fa5-a2a0-acff6523eee0.md) (`public`)
- [Exit Guide: leave ChatGPT with everything](/outputs/48767803-e666-4155-a8ee-73f62fd88d83.md) (`public`)
- [Ownership Score, worked example: 38/100](/outputs/4a733308-59bd-4ad4-b53d-f8d28356cc35.md) (`public`)
