It's Friday night, and I'm sitting at my desk, drinking a really, really good scotch, and coding a financial data website with nobody to share the magic with. Unacceptable! https://totalgrowthinvesting.com/history.php?symbol=URA

It's this new law that taxes any and all transfers of digital assets at 0.20%. Even transfers between wallets, in or out of exchanges, everything. It's not the stupidest idea I've ever heard, but it's really close.

Governor J.B. Pritzker is telling people not to spend money in his own state. This law tells me very clearly that the Governor and the Illinois House and Senate have no idea what they are talking about. But then I think 99% of our political leadership around the globe is just as foolish.

Show more

Yeah, really good idea. I've updated the skill to read from anything and output both .json and .docx so my wife can open the files in google docs. Thanks for the push!

I'm working on converting all of these into something my wife can use, we don't have an application designed specifically to read a schema and display it. Good idea though.

--- name: recipe-converter description: Convert recipe files of any format into clean, polished, consistently styled HTML. Use this skill whenever the user uploads a recipe file and asks to convert it, clean it up, or save it — regardless of source format (.htm, .shtml, .html, .doc, .txt, .eml, .pdf, Google Doc, etc.). Also trigger when the user says "please convert this recipe", "clean up this recipe", "process this recipe", or pastes recipe text and wants a formatted version. Works for individual recipes or batches. The output is a warm, elegantly styled HTML file ready to save and share. --- # Recipe Converter Convert recipe files of any format into clean, polished HTML — stripping away all cruft (navigation, ads, FrontPage artifacts, SSI includes, copyright boilerplate, branding) and leaving only the actual recipe content, beautifully formatted. ## When this skill applies - User uploads any file and asks to convert or clean up a recipe - User says "please convert this recipe", "process this recipe", "clean this up" - User pastes raw recipe text and wants formatted output - User is working through a batch of recipe files folder by folder - Source may be: .htm, .shtml, .html, .doc, .txt, .eml, .mht, .pdf, Google Doc link, or plain pasted text ## Step 1: Read the source Use the appropriate method for the file type: - `.htm`, `.shtml`, `.html`, `.txt`: `view` the file directly - `.doc`, `.docx`: use the docx skill or `bash_tool` with python-docx - `.eml`: `view` as text, extract body content - `.pdf`: use the pdf-reading skill - Google Doc URL: use `google_drive_fetch` - Pasted text: use as-is from the conversation ## Step 2: Extract and clean Read with comprehension. Identify and keep: - Recipe title - Yield / servings / timing (prep, cook, total) - Description or headnote (if present) - Ingredient list(s) — may be grouped into sub-sections (dough, filling, icing, etc.) - Instructions / steps - Make-ahead notes, tips, or technique callouts - Source attribution (author, publication, date) - Nutrition info (if present — format as a single clean line) - Dietary tags (Dairy Free, Vegetarian, Gluten Free, etc.) Discard everything else: - Navigation bars, headers, footers - SSI includes (``) - FrontPage/Dreamweaver metadata - Ads, promotional copy, brand trademarks (® ™) - "Rate this recipe", share buttons, comment sections - Unrelated page content ## Step 3: Editorial improvements Apply these consistently — this is where the skill adds real value: **Ingredients:** - Convert fractions to proper Unicode characters: ½ ¼ ¾ ⅓ ⅔ ⅛ ⅜ ⅝ ⅞ - Standardize abbreviations: tablespoon → Tbsp, teaspoon → tsp, ounce → oz, pound → lb - Remove brand names where generic terms work (e.g. "McCormick® Italian Seasoning" → "Italian seasoning") - Move equipment items out of ingredient lists (e.g. "12 muffin cups" → mention in instructions) - If an ingredient is used in two stages, note "divided" after it - If water or another liquid is listed only in instructions but not ingredients, add it to the list - Group into sub-sections when the recipe has distinct components (dough / filling / topping / sauce) **Instructions:** - Break dense paragraphs into individual numbered steps — one clear action per step - Pull "preheat oven" out as its own first step if it's buried in a paragraph - Fix vague references like "add next 7 ingredients" — name the actual ingredients - Preserve technique tips inline where they're most useful - Fix encoding artifacts: `\xb0` → °, `\xe9` → é, `\xfc` → ü, `\x97` → —, `\x99` → (remove), etc. **Special callout blocks** (use when content warrants): - Overnight/advance warning → highlighted note at top - Braiding, rolling, or technique tips → tip block - Make-ahead instructions → make-ahead block - Dietary tags → pill tags under the title ## Step 4: Generate the HTML Use this exact template and CSS. Do not deviate from the visual style — consistency across all recipes is the goal. ```html [RECIPE TITLE]

``` ## Step 5: Save and present Use `create_file` to write the output to `/mnt/user-data/outputs/[recipe-slug].html`, then call `present_files` so the user can download it directly. **Always derive the output filename from the recipe title**, not the source filename. Convert the recipe title to a lowercase hyphenated slug, dropping common filler words (a, an, the, and, with, on, in, of) and punctuation: - "Mango Salmon on a Bed of Wild Rice" → `mango-salmon-wild-rice.html` - "Mom's Best Chocolate Chip Cookies" → `chocolate-chip-cookies.html` - "Slow Cooker Chicken and Dumplings" → `slow-cooker-chicken-dumplings.html` Source filenames — whether they include a site name, path prefix, or any other origin indicator — should be ignored when naming the output. The goal is a clean, recipe-focused filename that reflects what the dish actually is. ## Category footer values Use the folder/category the user is currently working on. Current known categories: `bread` · `Breakfast` · `casseroles` · `Chicken` · `dessert` · `drinks` · `greek` · `Kids` · `Main` · `Meat` · `Pasta` · `Salad` · `Seafood` · `sides` · `Soup` · `Spices_Dressings` · `Steak` If converting from Google Drive or another source with no clear category, omit the category or ask the user. ## Quality checklist before saving - [ ] All SSI includes and FrontPage artifacts removed - [ ] Fractions converted to Unicode characters - [ ] Encoding glitches fixed (°, é, ü, —, etc.) - [ ] Brand trademarks stripped - [ ] Equipment removed from ingredient list - [ ] Dense paragraphs broken into numbered steps - [ ] "Preheat oven" is step 1 if applicable - [ ] Vague ingredient references ("next 7 ingredients") replaced with actual names - [ ] Advance-prep warning shown as .note if needed - [ ] Source attribution in footer if known - [ ] File saved and presented for download

Show more

Anyone here have a bunch of recipes downloaded in tons of different formats from all kinds of websites over the last 30 years? We do. And I created a skill in Claude to take any recipe file, in any format, and output it into a clean and self-contained .html file that looks good and preserves the recipe as intended.

Show more

I have always, ALWAYS, considered CPI to be a lie, a story we are told so we don't get scared of the future. And the longer they have repeated that lie, the more obvious it becomes that it is a lie, and we stop trusting anything else they say. But the narrative of that lie is bound up in identity, in tribal connections and agreements, it's part of the very commitment structures that keep this country alive and functioning. And it's ALL A LIE. It has gotten to the point where I don't believe anything that ANYONE in government says without direct proof that the conclusions presented to me are based on evidence that I can personally verify. Which is rare or difficult in the best of circumstances, and nearly impossible now. How can we trust someone who repeats obvious falsehoods again and again like they believe it, when the evidence to the contrary is available to anyone who can type into a keyboard?

Show more

A client designed for a particular niche has its place in the market. There's nothing wrong with it, and it doesn't affect anyone outside of that tribe.