Jonathan Mast
14.6K posts

Jonathan Mast
@jonathanmast
Simple tips to leverage AI prompts at work. | Follow for tips and tricks to get things done WITH AI.
Alabama, USA Katılım Şubat 2010
15.8K Takip Edilen26.9K Takipçiler

Base44 - you may have some of the worst customer support in 2026! Days and Days waiting for billing support ... after I've paid for multiple account.
I'm not impressed.
If this message happens to be read by anyone that cares about keeping customers please contact me at jonathan@whitebeardstrategies.com
English

Join me next week and learn Skills + get over a dozen Skills just for attending! go.whitebeardstrategies.com/ai-operators-l…
English

Get a 30 Day FREE Trial of GHL at bit.ly/wbs-ghl + Get FREE Access to my growing GHL Training library!
*Affiliate link
English

Join me next week and learn Skills + get over a dozen Skills just for attending! go.whitebeardstrategies.com/ai-operators-l…
English

Use this prompt to build your first SKILL file:
Prompt
You are an expert AI systems architect specializing in creating SKILL.md files for AI coding agents (Claude Computer Use, Manus, and similar agentic systems). You have deep expertise in prompt engineering, tool orchestration, and designing reproducible agent workflows.
Background: SKILL.md files are structured instruction sets that live in an agent's skills directory and are read BEFORE the agent begins work. They act as a playbook — telling the agent when to activate, what to install, what steps to follow, and how to validate output. The best SKILL files are direct, imperative, and leave no ambiguity for the agent.
Create a complete, production-ready SKILL.md file for the following:
**Skill Purpose:** {{skill_purpose}}
**Desired Outcome:** {{desired_outcome}}
The file must include these sections:
1. **Header** — Skill name, one-line description, and trigger conditions (when should the agent use this skill)
2. **Dependencies** — Required packages/libraries with exact install commands and verification steps
3. **Workflow** — Numbered step-by-step instructions from input to final output, including file paths (working dir: /home/claude, output: /mnt/user-data/outputs/), decision points, and error handling
4. **Code Template** — A working reference implementation the agent can adapt, with inline comments and edge case handling
5. **Quality Checks** — Validation steps the agent must run before delivering output, common failure modes, and fixes
6. **Usage Notes** — Best practices, limitations, and any related skills
Write all instructions in direct, imperative language ("Do X" not "You should consider X") since the reader is an AI agent. Format as valid Markdown ready to save as SKILL.md. Use code blocks for all commands and scripts.
Ask me any questions you have.
English

I'm deleting this post in 24 hours.
i just upgraded my Seedance 2.0 guide from 200 to 400+ prompts.
→ 200+ fresh prompts nobody has posted yet
→ Audio-to-video workflows that feel illegal
→ Shot list templates replacing $5K video editors
→ A monetization blueprint worth more than paid courses
People in my DMs are already making money with the first version.
This upgraded version shouldn't be free.
And after today, it won't be.
♻️ Repost + comment "VIDEO" → DM in 30 mins.
Note: (follow me first, or I can't send it)
GIF
English