Skip to main content
在 Manus 中运行任何 Skill
一键导入
GitHub 仓库

show-and-tell

show-and-tell 收录了来自 wan-huiyan 的 2 个 skills,并提供仓库级职业覆盖和站内 skill 详情页。

已收集 skills
2
Stars
0
更新
2026-07-08
Forks
0
职业覆盖
1 个职业分类 · 已分类 100%
仓库浏览

这个仓库中的 skills

show-and-tell
网页开发工程师

Turn dense technical findings, an analysis, a code/research session outcome, or a jargon-heavy document into a genuinely PLAIN-ENGLISH self-contained HTML explainer a non-technical or busy stakeholder can actually understand AND trust — built on a single everyday metaphor carried through the whole piece (the bad news included), with the REAL numbers shown honestly beside each plain claim, an "engineer's note" layer so technical readers aren't shortchanged, a foregrounded honesty/limits box, and a bundled FACT-VERIFIER that checks every claim, number, and metaphor back against the source document to catch translation drift before anyone reads it (self-contained, opens straight from file:// — no build, no server; arcade/pixel aesthetic). Use this WHENEVER the user wants to explain technical work in plain English, make a pretty/shareable report, one-pager, or recap, summarize an investigation/session "so my boss/team/client can understand it," translate jargon results for a lay audience, or asks for an explainer

2026-07-08
show-and-tell
网页开发工程师

Turn dense technical findings, an analysis, a code/research session outcome, or a jargon-heavy document into a genuinely PLAIN-ENGLISH self-contained HTML explainer a non-technical or busy stakeholder can actually understand AND trust — built on a single everyday metaphor carried through the whole piece (the bad news included), with the REAL numbers shown honestly beside each plain claim, an "engineer's note" layer so technical readers aren't shortchanged, a foregrounded honesty/limits box, and a bundled FACT-VERIFIER that checks every claim, number, and metaphor back against the source document to catch translation drift before anyone reads it (self-contained, opens straight from file:// — no build, no server; arcade/pixel aesthetic). Use this WHENEVER the user wants to explain technical work in plain English, make a pretty/shareable report, one-pager, or recap, summarize an investigation/session "so my boss/team/client can understand it," translate jargon results for a lay audience, or asks for an explainer

2026-07-08