AI Services Market
AI Services Market › Fabrique de compétences › Images › Internal Tools OG Image
$4.99 · Sans inscriptionv1.0.0– vues

Internal Tools OG Image

Une carte d'aperçu 1200×630 propre, pour que vos outils internes ressemblent à de vrais produits dans Slack.

Transforme votre IA en designer d'aperçus sociaux pour les outils internes — elle crée une image OG 1200×630 propre pour tableaux de bord, panneaux d'administration et outils d'équipe, qui rend nette dans Slack, la documentation et les aperçus de liens.

Aperçu de Internal Tools OG Image
Idéal pour
Créateurs d'outils internes, équipes plateforme et developer advocates
Temps nécessaire
~20 min
Niveau
Accessible aux débutants

Installez-la en 3 étapes

Sans inscription. Sans outils en ligne de commande. Choisissez votre IA, copiez une ligne, collez-la.

Pro — les 511 compétences

Vous préférez le faire vous-même ? Achetez la compétence ($4.99), téléchargez le ZIP depuis votre confirmation d'achat, décompressez-le dans le répertoire indiqué ci-dessus, redémarrez votre session IA — même résultat. Vous l'avez déjà achetée ? Votre assistant IA peut la télécharger pour vous.

Contenu du pack

Un fichier SKILL.md (le guide pratique) + un modèle de départ. Aperçu :

Internal Tools OG Image

When to use

  • You built an internal dashboard, admin panel, or team tool and its link preview in Slack shows a blank gray box
  • You're sharing an internal tool in docs, a wiki, or a team announcement and want the link to look like a real product
  • Your team ships several internal tools and they all need consistent, recognizable preview cards
  • You're demoing an internal tool externally (conference talk, blog post, portfolio) and the preview is the first impression
  • A tool's preview currently shows a screenshot full of real user data — a privacy problem you need to fix

Workflow

  1. Collect the tool's identity (input: tool name + purpose → output: identity brief)
    Gather the essentials: the tool's name, one line on what it does, its brand color or the team's neutral palette, and whether it has a logo or mark. Decide what the preview should communicate to someone who has never seen the tool: usually the name + one line of purpose + a hint of the interface. If the tool has no brand at all, pick a neutral dark or light background with one accent color — an OG image for an internal tool should look intentional, not like a screenshot accident.
  2. Design the 1200×630 composition (input: identity brief → output: layout spec)
    Lay out the standard anatomy: left side for text (tool name in large type, one-line purpose underneath), right side for a small visual (a simplified dashboard mock, a glyph, or an abstract mark). Keep the safe zone in mind — text must stay clear of the edges and the center, because different platforms crop previews differently. Choose a background that reads at thumbnail size: flat color, subtle gradient, or a faint grid. If the tool's real UI is part of the visual, use a sanitized mock with fake data, never a screenshot of production.
  3. Build the image (input: layout spec → output: draft OG image)
    Produce the image at exactly 1200×630 pixels. Type must be large — the name should be readable in a Slack sidebar preview at roughly 300 pixels wide, which means headline type around 64–80px at full size. Keep the total word count under 12: name + one line. Export as JPG or PNG under 300KB so it loads fast in every preview crawler. Check the draft at three sizes: full, Slack-width, and tiny (a phone notification) — if the name isn't legible at tiny size, the type is too small or the composition too busy.
  4. Wire it into the tool (input: draft OG image → output: live preview)
    Add the standard meta tags to the tool's pages: og:image pointing at the image URL, og:title with the tool name, og:description with the one-line purpose, and twitter:card set to summary_large_image. Serve the image from a stable, publicly reachable URL — preview crawlers can't log in, so an image behind auth will render as nothing. If the tool is internal-only, host the image on a public static path or the team's public site and point the tags there.
  5. Verify across platforms (input: live preview → output: verified OG image)
    Test the link in Slack, in a doc or wiki embed, and in at least one social preview debugger. Confirm: the image loads, the name is legible, nothing is cropped awkwardly, and no real user data appears anywhere in the visual. Re-check after any rebrand or rename — stale OG images are how a renamed tool keeps showing its old name in every chat for a year.

Aperçu du modèle

Internal Tools OG Image — Template

One tool = one OG image. Fill this in before designing.

Identity brief

Tool name: {name} One-line purpose: {what it does — under 8 words} Palette: {background + one accent color} Logo / mark: {file or "none — use glyph / abstract mark"} Visual on the right: {simplified dashboard mock with fake data / glyph / abstract mark}

Layout spec (1200×630)

  • Background: {flat color / subtle gradient / faint grid}
  • Left: tool name at {64–80}px + one-line purpose below
  • Right: {visual description}
  • Safe zones: text clear of edges and center (platforms crop differently)
  • Total words: ≤12

Le pack de compétence lui-même (SKILL.md + modèle) est rédigé en anglais.

Pro — les 511 compétences

Vous aimerez aussi