agentleFS
passion4it-gmbhpassion4it-gmbh/passionfruit-site/.claude/skills/new-post/SKILL.md

new-post

Skill0 starsChanged 12 days agoMITView on GitHub

Create a new bilingual blog post with proper frontmatter and both DE/EN files.

  • Reads credentials
  • Commits and pushes

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. imMamdouhaboammar/linkedin-animated-infographics★ 14same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a bilingual (DE + EN) blog post with correct frontmatter, real content, and a commit.

    line 8
  2. Distinctive:

    Ask these ONE AT A TIME using the AskUserQuestion tool:

    line 12
  3. Distinctive:

    If the user gave a German title, translate it for the EN version (and vice versa).

    line 30
  4. Very specific:

    Check if OPENAI_API_KEY is set, in .env or the environment.

    line 87
  5. Very specific:

    If the key is missing, leave heroImage out and move on.

    line 97

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Create a New Blog Post

Create a bilingual (DE + EN) blog post with correct frontmatter, real content, and a commit.

Gather info

Ask these ONE AT A TIME using the AskUserQuestion tool:

  1. "What's the blog post about? Give me a title or topic."
  2. "What should it say? Notes, bullet points or a rough draft are all fine."
  3. "Who's the author?"
  4. "Any tags? Pick from: KI/AI, Webentwicklung/Web Development, Design, Business, Tutorial — or add your own."

Write the post

Write the post in both languages from what the user gave you. Each language should read as if a native speaker wrote it. You can explain general topics, but don't invent facts about the business, customers or numbers. Show the user the draft and adjust it before committing. Never commit placeholder text, because it would go live.

Generate identifiers

  • translationKey: derive from the English version of the title, kebab-case, ASCII-only (e.g., "websites-with-ai"). This is shared across both locale files.
  • DE slug: German-friendly kebab-case filename (e.g., webseiten-mit-ki.md)
  • EN slug: English-friendly kebab-case filename (e.g., websites-with-ai.md)
  • Asset slug: short kebab-case name for the hero image (e.g., ai-websites)

If the user gave a German title, translate it for the EN version (and vice versa). Both titles should feel natural in their language.

Localize tags

Tags must match the locale. Use these pairs:

DE tagEN tag
KIAI
WebentwicklungWeb Development
DesignDesign
BusinessBusiness
TutorialTutorial
UnternehmenCompany

For custom tags, translate them appropriately.

Create the files

src/content/blog/de/<de-slug>.md

---
translationKey: "<translationKey>"
title: "<German title>"
description: "<German description — one sentence summarizing the post>"
publishedAt: <today's date as YYYY-MM-DD, no quotes>
author: "<author>"
tags: ["<DE tags>"]
heroImage: "../../../assets/blog/<asset-slug>.png"
featured: false
---

<German post body>

src/content/blog/en/<en-slug>.md

---
translationKey: "<translationKey>"
title: "<English title>"
description: "<English description — one sentence summarizing the post>"
publishedAt: <today's date as YYYY-MM-DD, no quotes>
author: "<author>"
tags: ["<EN tags>"]
heroImage: "../../../assets/blog/<asset-slug>.png"
featured: false
---

<English post body>

Only include heroImage if the image file exists. A path to a missing file fails the whole build. Posts work fine without one.

Hero image

Check if OPENAI_API_KEY is set, in .env or the environment. If it is, ask:

"Want me to generate a hero image for this post?"

If yes, run:

pnpm generate-image "<descriptive prompt for the topic>. Editorial photography style, modern and clean. No text, no logos." -o src/assets/blog/<asset-slug>.png --size 1536x1024

If the key is missing, leave heroImage out and move on.

Commit

IMPORTANT: Never commit a single-locale entry. Both DE and EN files must exist before committing.

Stage both files (and the image if generated), then commit:

git add src/content/blog/de/<de-slug>.md src/content/blog/en/<en-slug>.md src/assets/blog/<asset-slug>.png  # image only if generated
git commit -m "feat: add blog post — <translationKey>"

In a cloud session, also push: git push -u origin HEAD.

Tell the user the post is saved in both languages. In a local session, start pnpm dev yourself and give them the link. In a cloud session, tell them it appears on the preview link once the pull request is open, or on the site once it's merged.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.