Update to Fountain

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,22 +1,13 @@
 ---
 name: fountain-onboarding
-description: Set up Fountain. Trigger on first use, when asked, when preferences are empty, or when a skill is missing something.
+description: Set up Fountain: show, channels, clip look, preferences, and Daily Growth. Use on first use or on request.
 ---
 
 ## Overview
 
-This skill ensures that the user can effectively use Fountain API and skills.
-
-It makes sure that:
-
-- Fountain API is reachable.
-- Fountain skills are installed.
-- Project preferences are recorded.
-- Relevant software is installed.
-- Any other blockers are resolved.
-
-You MUST go through each outstanding item, even if the task does not require some of the above.
-This way, you do not need to ask the user again later.
+This skill gets a podcaster from a new Fountain account to fresh clips in their own style each morning.
+It walks the user through the setup, fixes what it can, and links to the rest.
+The last step is a short guide to the daily drafts.
 
 ## Input
 
@@ -24,47 +15,53 @@
 
 ## Output
 
-- Updated preferences.
-- A scheduled run of skill **fountain-daily-growth**.
+- A project with a show, connected channels, and Daily Growth on.
+- Updated preferences: Brand, Editorial, Accounts, and the Narratives of the show.
 - A summary in the chat: what changed, what is still missing, and who must act on it.
-- A next step: return to the task that triggered this skill, or offer a first run of skill **fountain-clip-finder**.
+- A short guide to the daily work with the drafts.
 
 ## Housekeeping
 
 You MUST read HOUSEKEEPING.md if you haven't already.
 
+## Requirements
+
+- Fountain API.
+
 ## Process
 
-1. Ensure you are in a fully capable agent environment, such as Claude Code or Codex.
-   Otherwise, suggest that the user uses such an environment to take full advantage of Fountain.
-2. Ensure you have access to Fountain API by fetching the user's projects.
+1. Fetch the projects of the user, to make sure that Fountain API is reachable.
    An empty array is fine, as long as the status is 200.
-   If you don't have access, install the plugin from https://github.com/fountain-fm/fountain-skills
-3. Ensure you have access to Fountain skills: **fountain-clip-finder**, **fountain-clip-producer**,
-   **fountain-daily-growth**, and **fountain-reports**.
-   If you don't have access, install the plugin from https://github.com/fountain-fm/fountain-skills
-4. Ensure that the user has at least one project.
-   Otherwise, link to https://fountain.fm/studio/onboarding?kind=PODCAST
-5. Ensure that the project has at least one podcast.
-   Otherwise, link to https://fountain.fm/studio/{project_id}/onboarding?kind=PODCAST
-6. If there are no connected social channels, suggest connecting YouTube, X, or Instagram via the Social API.
-7. Ensure the project preferences specify the source of clip material, automation (auto-render, etc.),
-   email addresses to send the reports to, and any other relevant details.
-8. When running locally, ensure all relevant software is installed: Python 3.11 or above, yt-dlp,
-   ffmpeg + ffprobe (the most complete version that includes libass, drawtext, fontconfig and whisper,
-   e.g. Homebrew `ffmpeg-full`), OpenCV 4.8 or later, ImageMagick, and a whisper.cpp model file
-   (`ggml-base.en.bin` in `~/.cache/whisper`).
-   If something is missing, attempt to install it yourself.
-   If you cannot install it, make it easy for the user to install it themselves, even if they are non-technical.
-9. Research the look of the show: its artwork, its website, and its existing clips.
-   Write out brand guidelines from that research.
-   Choose the caption style (using skill **fountain-clip-producer**), color, and font.
-   Record the guidelines, and the logo URLs if available.
-   Don't include logos in the clip settings unless existing clips have them.
-   Present a mockup of what the clip will look like.
-   Offer to customize the style on the clip styling page.
-10. Set up automatic daily growth using skill **fountain-daily-growth**.
-    Record its time and the machine that runs it under Automation.
+   If the API is not reachable, install the plugin from https://github.com/fountain-fm/fountain-skills
+2. Make sure that the user has at least one project.
+   Otherwise, link to https://fountain.fm/studio/onboarding, where the user also chooses a plan.
+3. Make sure that the project has at least one show.
+   Otherwise, connect the show with the Project API, or link to
+   https://fountain.fm/studio/{project_id}/onboarding?kind=PODCAST
+   A connected show costs one credit for each episode with no transcript.
+   Tell the user this cost before you connect the show.
+4. Make sure that the project has at least one social channel, e.g. X, YouTube, or Instagram.
+   Connect it with the Social API, and send the user the link that approves access.
+   Daily Growth writes one post for each connected channel.
+5. Choose the look of the clips.
+   Read the caption styles and the settings that Fountain renders on the clip rendering page.
+   Look at the artwork of the show, its website, and its existing clips.
+   Propose one caption style, with colors and a font that match the show, and record them under Brand.
+   Link the clip rendering page, where the user can preview each style.
+6. Record the rules for the words of each post under Editorial, e.g. emoji, hashtags, and tone.
+   Record the handles of people that posts tag under Accounts.
+7. Show the user the Narratives of the show, and change them as the user says.
+   When the show has none, write a few from its recent episodes.
+8. Load the automations of the project with the Project API, and explain each one in one sentence.
+   Turn on Daily Growth, unless the user declines.
+   Another automation stays off until the user agrees to it.
+9. Describe the daily routine to the user, in a few lines:
+   - With Daily Growth on, Fountain finds new clips each day, drafts their posts, renders the videos, and emails
+     a report.
+     The report goes to each project member who can access the show.
+   - The user approves and schedules each draft at the `drafts_url`, or tells the agent to do it.
+   - To change a clip, the user tells the agent, e.g. "make the captions bigger on my latest clip".
+   - Each post that goes out uses one credit.
 
 ## Additional notes
 
@@ -74,20 +71,15 @@
 
 Onboarding must not feel overwhelming:
 
-- Record the Fountain defaults below.
-  Then present them for the user to confirm, and offer customization as an option.
-  Do not present all options unless the user chooses to customize.
+- Choose the defaults yourself, record them, and then present them for the user to confirm.
+  Say that the user can change each one.
+- Do not present all options unless the user chooses to customize.
 - Do not provide unnecessary information.
-- When appropriate, make a decision yourself but offer customization.
-
-Fountain defaults:
 
-- Each report delivered as email, under Reporting.
-- `performance` and `review-posts-simple` as two separate reports, under Reporting.
-- Auto-render on, under Automation.
-- 3 clips per day, under Automation.
+A request to run Daily Growth each day means: turn on the Daily Growth automation.
+This skill installs no software, because Fountain renders the clips.
 
-When no user is present, e.g. in a scheduled run, do only the steps that need no answer from the user.
+When no user is present, do only the steps that need no answer from the user.
 Report what is still missing, so that the user can complete it in the next chat.
 
 When this skill is triggered as part of a specific task, explain to the user why they need to go through this skill.