How do I install the Short Form Present Vs Future skill?

Run npx skillmds@latest add r-bart/short-form-present-vs-future in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Short Form Present Vs Future safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Short Form Present Vs Future?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Short Form Present Vs Future free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Short Form Present Vs Future?

r-bart (@r-bart) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Short Form Present Vs Future by r-bart

Name: Short Form Present Vs Future
Author: r-bart

Short Form Present Vs Future

Short-form (X / LinkedIn) comparison of how something is done today vs how it will be done in 1–5 years. Strong for tech / AI / tooling takes. Use when the user wants to frame a directional bet, a tooling shift, or an obsolescence call — anything where the punchline is "this is the present; here's the future".

r-bart 2d160db 2.5 KB Updated Sep 17, 2026

File contents

Metadata

inherits: ../short-form-voice-adjustments/SKILL.md
formats: X single, X thread, LinkedIn

short-form-present-vs-future

Compare how a thing is done today vs how it will be done — soon, or with a new tool, or after a shift. Adjacent to short-form-x-vs-y, but the contrast is temporal: now vs next.

Structure (LinkedIn)

[Hook: the contrast in one line.
  Examples:
  - "Writing tickets used to take me 3 hours. Now it takes 3 minutes. Same quality."
  - "Last year: 9 SaaS subscriptions for product management. This year: 1 chat thread."]

[Today: 2-3 lines on the current way. The cost, the friction, the time.]

[Tomorrow (or now, with the new approach): 2-3 lines on the new way. Concrete tools, workflow, output.]

[The shift — 1-2 lines on what changed and why it matters.]

[Closer: the rule the shift implies.]

Rules

Both sides must be real and recent. "How we used to write code in 2010" is too far back to matter. "Last year" or "last quarter" is the sweet spot.
Specifics are everything. Number of hours, number of tools, name the tools. Vague present-vs-future is AI slop.
Don't predict — describe. If you're talking future, say what YOU are already doing differently. Don't speculate.
Land on a rule. The contrast itself isn't the post — the implication is.

Anti-patterns

Hype futurism without specifics ("AI will change everything!"). Banned.
"In 5 years…" predictions that you can't back up. Stick to what you've already changed.
Symmetry trap — listing 5 things old vs 5 things new with no insight. Pick the contrast that matters.
"RIP [old thing]" framing. Lazy.

Example shapes

Two illustrative present-vs-future framings (replace with shifts you're actually experiencing):

The reframed-obstacle shape: "The old way: spend 3 hours in dashboards. The new way: one /pulse command. The dashboards weren't the work — they were the obstacle."
The collapsed-toolchain shape: "Old: 9 tools for content. New: 1 doc + 1 cron. Same output."

For author-specific references in your voice, see writing-style/SKILL.md.

---name: short-form-present-vs-futuredescription: Short-form (X / LinkedIn) comparison of how something is done today vs how it will be done in 1–5 years. Strong for tech / AI / tooling takes. Use when the user wants to frame a directional bet, a tooling shift, or an obsolescence call — anything where the punchline is "this is the present; here's the future".---## Metadata- **inherits**: `../short-form-voice-adjustments/SKILL.md`- **formats**: X single, X thread, LinkedIn# short-form-present-vs-futureCompare how a thing is done today vs how it will be done — soon, or with a new tool, or after a shift. Adjacent to `short-form-x-vs-y`, but the contrast is temporal: now vs next.## Structure (LinkedIn)```[Hook: the contrast in one line. Examples: - "Writing tickets used to take me 3 hours. Now it takes 3 minutes. Same quality." - "Last year: 9 SaaS subscriptions for product management. This year: 1 chat thread."][Today: 2-3 lines on the current way. The cost, the friction, the time.][Tomorrow (or now, with the new approach): 2-3 lines on the new way. Concrete tools, workflow, output.][The shift — 1-2 lines on what changed and why it matters.][Closer: the rule the shift implies.]```## Rules- **Both sides must be real and recent.** "How we used to write code in 2010" is too far back to matter. "Last year" or "last quarter" is the sweet spot.- **Specifics are everything.** Number of hours, number of tools, name the tools. Vague present-vs-future is AI slop.- **Don't predict — describe.** If you're talking future, say what YOU are already doing differently. Don't speculate.- **Land on a rule.** The contrast itself isn't the post — the implication is.## Anti-patterns- Hype futurism without specifics ("AI will change everything!"). Banned.- "In 5 years…" predictions that you can't back up. Stick to what you've already changed.- Symmetry trap — listing 5 things old vs 5 things new with no insight. Pick the contrast that matters.- "RIP [old thing]" framing. Lazy.## Example shapesTwo illustrative present-vs-future framings (replace with shifts you're actually experiencing):- The reframed-obstacle shape: _"The old way: spend 3 hours in dashboards. The new way: one /pulse command. The dashboards weren't the work — they were the obstacle."_- The collapsed-toolchain shape: _"Old: 9 tools for content. New: 1 doc + 1 cron. Same output."_For author-specific references in your voice, see `writing-style/SKILL.md`.

Frequently asked questions