浦江翻译

SKILL效率
效率 未标注权限 许可证不明确
安装这个技能

浦江翻译 — Chinese-English terminology for the Pujiang Innovation Forum (浦江创新论坛), covering the 2025 (18th) and 2026 (19th) editions from the official handbooks (2026 is a bilingual edition: Chinese half + English half) AND the official bilingual agenda site (pujiangforum.cn/zh|en/forum/schedule). Priority: 官网 ≧ 2026 手册英文部分 > 2026 手册中文部分夹带的英文 > 2025 手册 (the site wins only where it disagrees with the handbook's English half). Covers forum/sub-forum names, forum topics, venues, rooms, hotels, organizations, people & titles, future-industry topics, agenda segment labels, branded releases, partner tiers and page indexes. Use when the user needs to translate, label, or build a bilingual glossary of 浦江创新论坛 / Pujiang Innovation Forum terms in either direction (ZH⇄EN), or to find which handbook page a topic appears on.

一句话选型结论

按资料字段整理

浦江翻译是效率类的 Agent Skill,安装方式未标注,权限级别未标注,许可证不明确,有可直接复制的安装命令。技能本质是给模型读的说明书,效果取决于模型与客户端;装完先用一个小任务验证,再放进正式流程。

分类效率 安装方式未标注 权限级别未标注权限 许可证许可证不明确
累计安装 未标注 本周 未标注
GitHub 星标 未标注 仓库 未标注
下载量 未标注 技能市场下载数
权限级别 未标注权限 安装前请确认风险范围
许可证 许可证不明确 未说明

安装

未标注
在支持 Skills 的客户端里执行,装完问一句「你有哪些技能」验证
skillhub install user_3a619c45/pujiang-translation
  1. 1
    确认客户端支持

    确认你的客户端支持 Skills(Claude、Codex、Cursor 等),并升级到较新的版本。

  2. 2
    拿到技能文件

    执行上面的命令安装;也可以把仓库里的 SKILL.md 手动放进客户端的 skills 目录。

  3. 3
    刷新技能列表

    重新打开客户端,或刷新技能列表,让新放进来的技能被加载。

  4. 4
    验证是否生效

    问一句「你有哪些技能」,确认列表里出现它,再拿一个小任务试跑。

技能档案

效率
字段来自技能仓库与公开索引,中文说明由本站标注
作者 / 维护方user_3a619c45仓库 未标注 · 版本 未标注
宿主客户端未标注技能可被这些客户端加载
安装方式未标注安装包 community
权限级别未标注权限安装前请确认风险范围
许可证未说明许可证不明确,商用前请自行确认条款
仓库可用性available技能仓库当前是否可访问
最近核验未标注上游最后核验时间 · 数据更新 1791619550
正文体量15.2 KBSKILL.md 原文大小,越大说明说明书写得越细

典型使用场景

3 类
按分类整理的常见用法,具体以 SKILL.md 为准
整理待办与日程

把零散任务收进清单,排出优先级。

批量处理重复任务

把固定动作做成模板,重复执行。

把流程写成清单

把口头流程整理成可复用的步骤。

选择建议

装之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有可直接复制的安装命令,不用自己翻文档找入口。

先想清楚的地方

  • 没有标注权限级别,实际能做什么要装好后确认。
  • 许可证不明确,商用或二次分发前先到仓库确认条款。
  • 没有做站内核验,内容以作者仓库为准。
  • 技能只是说明书,实际效果取决于模型与客户端,装完先用小任务试一遍。

更适合

  • 需要在效率场景里给模型补一套做法的人。
  • 愿意先读一遍 SKILL.md、确认它会让模型做什么的人。

不太适合

  • 对许可证要求很严、必须明确可商用的人。
  • 只想装完就自动变强、不打算看说明书的人。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
技能权限级别安装方式累计安装宿主客户端安装命令
浦江翻译当前 未标注权限 未标注 未标注 未标注 有
Nano PDF 文档 联网访问 ClawHub 市场 424.9 万 OpenClaw 有
自动更新程序 浏览器控制 ClawHub 市场 296.4 万 OpenClaw 有
Gemini 助手 联网访问 ClawHub 市场 254.7 万 OpenClaw 有
word DOCX 文档 联网访问 ClawHub 市场 239.6 万 OpenClaw 有
Excel XLSX 前端 联网访问 ClawHub 市场 227.0 万 OpenClaw 有

SKILL.md 全文

15.2 KB
模型实际读到的说明书原文,来自技能仓库

浦江翻译 · 浦江创新论坛 中译英 ZH⇄EN (Pujiang Innovation Forum)

A self-contained bilingual (Chinese⇄English) terminology reference for the Pujiang Innovation Forum, merged from four official sources:

  • 2025(第十八届) — 《会议手册 2025.09.14-1.pdf》,全 88 页,289 条
  • 2026(第十九届)手册·中文部分 — 《2026浦江创新论坛会议手册-中文0910.pdf》69 页,官方原文对照 147 条(合并后新增 52 条 + 覆盖 2025 旧译 9 条)
  • 2026(第十九届)手册·英文部分 — 《2026浦江创新论坛会议手册-英文.pdf》108 页,121 条(15 条改写了中文册/2025 的旧译)
    > ⚠️ 这本所谓「英文版」实际是中英双语版:每个议题先排中文段、后排英文段,装订在同一份 PDF 里。
    > 它与《2026浦江创新论坛会议手册-中文0910晚.pdf》是同一文件(MD5 均为 c6f13a01c7fd9e11f58cb23f480d5b18)。
    > 中文页 ↔ 英文页固定偏移 26 页:PDF P41+n ↔ P67+n(n=0…23)。
  • 2026(第十九届)官网 — pujiangforum.cn 中英双版议程页,119 条(96 条官网独有或覆盖手册,23 条与手册英文部分一致)

> 优先级:官网 ≧ 2026 手册英文部分 > 2026 手册中文部分夹带的英文 > 2025 手册。
> 官网与手册英文部分同级——只有两者译法不一致时才以官网为准;两者一致时保留先出现者的来源并标记「一致」。
> 中文册里零散夹带的英文(如 National Independent Innovation Demonstration Zones Forum)低于英文册的正式译法。
> 大小写/空格差异(如 Future information vs Future Information、Co., Ltd. vs Co., LTD.)不算冲突。
> 被覆盖的旧译保留在 prev_en 字段与合并表的「备注」列中,便于追溯。
>
> 收录原则:只收官方原文对照。 2026 中文册中仅有中文、无官方英文的条目(原「推导」68 条 + 「未收录」80 条)曾于 2026-09-10 全部剔除;英文册到货后,其中 87 条已有官方英文并已重新收录,目前 541 条全部有英文。查不到即答「未收录」,绝不现编。

When to use

  • The user provides a Chinese forum term and wants English — e.g. "把『可控核聚变专题论坛』翻译成英文"、"主宾省是哪个,英文怎么说".
  • The user provides an English forum term and wants Chinese — e.g. "DongJiao State Guest Hotel 中文是什么".
  • The user wants a bilingual glossary table, an agenda/signage label list, or consistent ZH⇄EN naming for forum materials.
  • The user asks which handbook page a topic is on — use page_index["2025"] or page_index["2026"].
  • The user is producing bilingual slides, signage, an agenda, or a delegate pack for the forum and needs verified naming.

Core resources

All in references/:

File Role
pujiang_glossary.md Merged canonical (2025+2026), 16 categorized tables + both page indexes. Best for browsing/quoting.
pujiang_glossary.json Machine-readable merged data (see schema below). Best for Grep/lookup.
pujiang_glossary_2025.md Archive: original 2025 mapping (289 terms, 88-page index).
pujiang_glossary_2026.md Archive: curated 2026 mapping from the Chinese half, official-source only (147 terms + 59-page index).
pujiang_glossary_2026_en.md 2026 handbook English half — 8 sections (基本信息 / 主题 / 年度主题 / 分论坛 35 / 特别对话 / 会场 28 / 酒店 5 / 组织机构 72) + a final table of intra-handbook translation conflicts. Tier-1 source.
pujiang_official_web_2026.md Official website ZH⇄EN pairs (34 forum names + 9 forum topics + 14 rooms + 54 agenda segments + 4 branded releases). Tier-1 source, wins over the handbook when they disagree.
scripts/fetch_web_glossary.py Re-scrapes the official agenda API and regenerates the file above. Run it to refresh before each forum edition.
scripts/extract_en_handbook.py Extracts the bilingual handbook: python scripts/extract_en_handbook.py <pdf> [out.txt] — prints a page-language map plus ZH↔EN organizer pairs (offset 26). Use when a new edition's handbook arrives.

JSON structure:

{
  "meta": { "category_count": 16, "term_count": 541,
            "merge_rule": "官网 >= 2026手册英文部分 > 2026手册中文部分 > 2025手册",
            "stats": { "kept_2025": 289, "added_2026": 52,
                       "conflict_2026_wins": 9, "pending": 0, "derived": 0,
                       "enbook_added": 112, "enbook_overrides": 15,
                       "web_added": 88, "web_overrides": 8 } },
  "categories": [ { "id": "subforums", "zh": "分论坛与专题论坛名称",
                    "en": "Sub-forums & Special Forums",
                    "terms": [ { "zh": "…", "en": "…", "year": 2026,
                                 "note": null, "prev_en": "…", "conflict": true } ] } ],
  "page_index": { "2025": [ { "page": "P21", "content": "…" } ],
                  "2026": [ { "page": "P39", "content": "可控核聚变专题论坛" } ] },
  "lookup": { "zh_to_en": { "湖南省": ["Hunan Province"] },
              "en_to_zh": { "Hunan Province": ["湖南省"] } }
}

Term fields: year = which edition it came from · source = 官网 (official site) / 手册英 (2026 handbook English half) / 手册 (2025 handbook, or English snippets inside the 2026 Chinese half) · also_2026 = the 2026 handbook also attests it · also_web = the official site attests the same wording · also_enbook = the handbook's English half attests the same wording · prev_en + conflict = old wording that was overridden. note is always null — every entry is a verbatim official pair.

Priority (already applied in the merged data): 官网 ≧ 手册英 > 手册 > 2025. Where the site disagrees with the handbook's English half, source becomes 官网, conflict is true and the handbook wording moves to prev_en. Where they agree, source stays with whoever came first and also_web / also_enbook is set — the second source adds no new information, so provenance is preserved.

On any task, first Read references/pujiang_glossary.md for context and/or Grep references/pujiang_glossary.json for the term. Never guess a translation that is not in the reference.

Category ids

basic_info (论坛基本信息) · themes (论坛主题) · sections_toc (目录/章节标题) · venues (会场与场地) · transport (交通信息) · people_titles (人员与职务) · annual_themes (年度主题与四大方向/六类未来产业) · subforums (分论坛与专题论坛名称) · special_events (特别对话与配套活动) · organizations (组织机构) · rooms (会场与会议室房间名) · hotels (酒店与住宿) · partners (论坛合作伙伴层级/鸣谢) · forum_topics (各分论坛主题 Topic) · agenda_segments (议程环节通用名称) · releases (成果发布与品牌内容). The last three come from the official website.

Translation conventions

  1. Lookup first, never guess. Match the whole phrase against zh/en; return the paired value. When two English values exist for one Chinese term, prefer the one from a 2026 source (source: 官网 or year: 2026) over the 2025 one; mention the superseded wording only if the user asks about history.
  2. Only official wording exists here. Every entry is a verbatim pair taken from a handbook — safe for print/signage. There is no "inferred" or "pending" tier in this glossary.
  3. Coverage is now complete for 2026 — every one of the 541 entries has an official English. If a term is still absent, answer (未收录) — never invent, never infer. Known gap: 启点社区 and similar 2026-only side-venue nicknames are not in any official source.
  4. Proper nouns & venues. Keep the handbook's exact spelling/capitalization: ZhangJiang Science Hall, DongJiao State Guest Hotel, Hilton Shanghai Zhangjiang Science City, NATIONAL INNOVATION CENTER par EXCELLENCE (NICE). Do not "correct" casing.
  5. Future-industry topics. 未来信息 → Future Information, 未来材料 → Future Materials, 未来能源 → Future Energy, 未来健康 → Future Health, 未来空间 → Future Space, 未来制造 → Future Manufacturing. Note 2026 re-bucketed some forums (合成生物学 moved from 未来健康 to 未来制造) and added 科学数据 (Science Data) under 创新生态.
  6. Country/region pairings. 中白 → China-Belarus, 中德 → China-Germany, 中瑞 → China-Switzerland, 一带一路 → Belt and Road.
  7. 2026 entity changes. 主宾国 2025 白俄罗斯共和国 → 2026 南非共和国 / The Republic of South Africa; 主宾省 2025 辽宁省 → 2026 湖南省 / Hunan Province. Older values remain in the glossary as 2025 entries — answer with the year the user is asking about.
    6b. Y-HUBS was renamed in 2026 (important). 2025 handbook: 青年创新讲坛 Y-HUBS → Youth Innovation Forum (Y-HUBs). 2026 official site: Youth Innovation Hub(Y-HUBS) — Forum became Hub, and the site writes it without a space before the parenthesis. Always use the 2026 wording unless the user asks about 2025.
    6c. Venue floors: trust the English site over the Chinese handbook. For 张江科学会堂2楼张江厅B the Chinese handbook says 2楼 but the official English page says Zhangjiang Hall B, 3F, ZhangJiang Science Hall. The English wording is recorded as canonical; flag the discrepancy if the user is producing floor signage.
    6d. Two venues are spelled differently inside the 2026 handbook itself — always quote the 参会须知 wording unless the user is copy-editing an agenda page:
    | 中文 | 参会须知页(canonical) | 议程页 |
    |---|---|---|
    | 杨浦区复兴岛船台公园 | Fuxing Island Slipway Park | Chuantai Park, Fuxing Island(官网另有 Fuxing Island Shipyard Park) |
    | 徐汇区漕河泾会议中心 | Caohejing Conference Center | Caohejing Convention Center, Xuhui District |
    Others with three-way variants: AI 应用商店 = MetAI Hub·AI Application Store(参会须知)/ AI MATRIX STORE(议程页);JIC 静投中心 = JIC Jing'an Center / SHANGHAI ENGINE COMMUNITY.
    6e. Only 启点社区 still has no official English — answer (未收录) for it.
  8. Section headers are printed in ALL CAPS in the 2026 handbook (FORUM AGENDA, CONFERENCE INSTRUCTIONS, ACKNOWLEDGEMENTS). This is display styling — the canonical glossary keeps title case (Forum Agenda). Do not treat the caps as a translation difference.
  9. Page locator. page_index["2025"] uses the 2025 handbook's printed pages (P1–P88); page_index["2026"] uses the 2026 file's PDF page numbers (1–69), which differ from that handbook's printed folios. State which one you are citing.

Workflow

A. Single-term lookup

  1. Grep pujiang_glossary.json for the exact zh/en.
  2. Reply: 中文 → English, plus (官网修订,手册旧译:…) if source is 官网 and conflict is true, or (2026修订,2025旧译:…) if it is a handbook conflict.
  3. Not found → (未收录). Do not fill the gap with a guess.

B. Batch list / agenda translation

  1. Read the merged glossary once.
  2. Substitute canonical pairs.
  3. Emit a Markdown table 中文 | English | 备注 (or English | 中文 | 备注).
  4. Not in the glossary → (未收录). Never fabricate.

C. Build a categorized bilingual glossary

  1. Filter categories by id.
  2. Output categorized tables mirroring pujiang_glossary.md, keeping the 备注 column.

D. Page-locator query

  1. Pick the year the user means (default to the latest, 2026).
  2. Grep that year's page_index for the keyword; return the page code + content.

Notes & boundaries

  • Scope: 2025 (18th) and 2026 (19th) handbooks only. Other editions → 未收录.
  • The 2026 handbook is bilingual, so almost every 2026 Chinese term now has official English. On 2026-09-10 the 148 Chinese-only entries were removed, then the English half arrived and 87 of them were restored as official pairs (另 61 条英文册同样没有,仍答「未收录」).
  • The handbook contradicts itself in ~7 places (科技政策论坛 = Science & Technology Policy Forum / Innovation Policy Forum, 太空算力产业生态论坛 = Space Computing … / Space Computing Power …, 上海市科学技术委员会 = Science and Technology Commission of Shanghai Municipality / Shanghai Municipal Commission of Science and Technology, etc.). The full list is the final table of pujiang_glossary_2026_en.md. The merged glossary picked one per term and recorded the other in prev_en — surface the conflict when the user is producing printed material.
  • A handful of English renderings look machine-generated even in the official handbook (明珠启航 智算未来 → OPearlAl、上海未来产业基金 → Shanghai Engine Fund). They were excluded; answer (未收录) and warn the user rather than quoting them.
  • The official bilingual agenda site is now the top-priority source and is the only place many 2026 forum names have official English. To refresh it (e.g. when the agenda updates or for a new edition), run
    python scripts/fetch_web_glossary.py then python scripts/build_json.py.
  • The site's own English is occasionally inconsistent (e.g. Opening Ceremony vs Opening ceremony, Closing Ceremony vs Closing Remarks). The glossary keeps the majority/official-site variant; do not "fix" these into house style on your own — they are recorded verbatim.
  • Keep replies concise: a table for lists, one line for single lookups, a page code for page queries.
  • Regenerate outputs after editing any source .md:
    python scripts/build_json.py (reads the four year/source files → writes merged .md + .json).
  • Refresh pipeline for a new edition:
    1. python scripts/extract_en_handbook.py <new.pdf> raw.txt → page map + organizer pairs
    2. hand-curate into references/pujiang_glossary_2026_en.md
    3. python scripts/fetch_web_glossary.py
    4. python scripts/build_json.py
  • scripts/strip_unofficial.py removes non-official rows from the year files (back up before use).

常见问题

5 问
答案由本站依据条目字段整理
浦江翻译怎么安装?

在支持 Skills 的客户端里执行:skillhub install user_3a619c45/pujiang-translation。安装方式为未标注。装完刷新技能列表或重开客户端。

浦江翻译支持哪些客户端?

资料没有标注宿主客户端,但只要客户端支持 Skills(Claude、Codex、Cursor 等),一般都能加载。

浦江翻译权限高吗,安全吗?

权限级别为未标注权限。安装前先看它会读取或写入哪些内容。

浦江翻译收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于技能本身和所用的模型或客户端,正式使用前按作者说明确认。

浦江翻译用什么许可证?

许可证标注为 未说明(许可证不明确)。商用或二次分发前请到仓库确认条款原文。

热门专题

按场景挑技能
全部专题 →

技能内容以作者仓库为准;分类、权限级别与许可证状态的中文说明为中文整理,最近核验 未标注。