@1aboveio/core-skills 0.1.0 → 0.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@1aboveio/core-skills",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "description": "Shared writing and document foundation: house style, editorial review, Chinese polish, terminology, write-doc, distill-writing, doc-to-md and reg-parser.",
5
5
  "license": "MIT",
6
6
  "repository": {
@@ -8,6 +8,7 @@
8
8
  "url": "git+https://github.com/1aboveio/ai.git",
9
9
  "directory": "skills/distribution/packages"
10
10
  },
11
+ "homepage": "https://github.com/1aboveio/ai/releases?q=%401aboveio%2Fcore-skills&expanded=true",
11
12
  "keywords": [
12
13
  "pi-package",
13
14
  "agent-skills",
@@ -17,10 +18,6 @@
17
18
  "skills",
18
19
  "README.md"
19
20
  ],
20
- "publishConfig": {
21
- "registry": "https://registry.npmjs.org/",
22
- "access": "public"
23
- },
24
21
  "pi": {
25
22
  "skills": [
26
23
  "./skills"
@@ -30,6 +27,10 @@
30
27
  "id": "core",
31
28
  "core": "@1aboveio/core-skills",
32
29
  "coreSkills": [],
33
- "digest": "d7ec0e12b950f957cfd3f2c87a1e27a7a5eca353ca875b639b43a46fed9dadee"
30
+ "digest": "b1f5b1215ab0f95e00d4f4b241395c263880644644d92aadeeeda4535e60d33b"
31
+ },
32
+ "publishConfig": {
33
+ "registry": "https://registry.npmjs.org/",
34
+ "access": "public"
34
35
  }
35
36
  }
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: distill-writing
3
3
  description: "Learn a house writing style from approved sample documents into the project's WRITING.md and writing/templates/, with evidence per rule, conflicts surfaced and manual edits kept. Use when given reference documents to learn from, or to set up or refresh the house style. NOT for writing a document (write-doc)."
4
- release-version: 0.36.0
4
+ release-version: 0.38.0
5
5
  ---
6
6
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
7
7
  # Distill a writing style
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: doc-to-md
3
3
  description: "Convert documents (PDF, DOCX, PPTX, XLSX, images) to Markdown so agents can read them. Use as the preprocessing step whenever binary files need to enter agent context — contract review, compliance audit, document analysis, evidence review."
4
- release-version: 0.36.0
4
+ release-version: 0.38.0
5
5
  ---
6
6
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
7
7
  # doc-to-md
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: editorial-review
3
3
  description: "Review a document or generated report for what it says (does the reader get the answer, is the argument sound, is anything unsupported, obvious or repeated), then fix the content. Use to review, tighten or clarify a doc or report, and as the review step of write-doc and the report skills. NOT for Chinese wording (polish-cn) or code review (better-review)."
4
- release-version: 0.36.0
4
+ release-version: 0.38.0
5
5
  ---
6
6
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
7
7
  # Editorial review
@@ -3,7 +3,7 @@ name: house-style
3
3
  description: "Shared reference the writing skills read by path: WRITING.md lookup and precedence, template choice, gap markers, template shape, the bundled templates, and the default English and Chinese style guides. Never select or invoke it as a task."
4
4
  disable-model-invocation: true
5
5
  user-invocable: false
6
- release-version: 0.36.0
6
+ release-version: 0.38.0
7
7
  ---
8
8
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
9
9
  # House style
@@ -54,6 +54,9 @@ trade-offs add up to. A reference section or a policy statement stays neutral.
54
54
  - Most sentences under 25 words; instructions under 20.
55
55
  - Present tense for how things are. "Will" only for what happens later.
56
56
  - Put the common case first and exceptions after.
57
+ - Write full sentences, not telegraphic notes. Keep the words that carry the logic: if,
58
+ when, because, but. Without them a rule becomes a label the reader has to decode.
59
+ Example: "It is 0 if there were no collections," not "0 when none."
57
60
  - Introduce a list with a complete sentence; keep list items parallel.
58
61
  - Use periods, not semicolons. Replace a dash aside with a new sentence.
59
62
 
@@ -82,6 +85,12 @@ trade-offs add up to. A reference section or a policy statement stays neutral.
82
85
  - No slashes: "a, b, or both", not "a/b" or "and/or". No "(s)" plurals. No "etc."; say up front
83
86
  that a list is partial.
84
87
  - No idioms, metaphors or Latin abbreviations (e.g., i.e., viz.); write "for example", "that is".
88
+ - Give every range its endpoints and say which are included: "from 00:00 up to, not including,
89
+ 06:00", not "between midnight and 6".
90
+ - When "and" and "or" meet in one condition, group them: "verified, and either a person or a
91
+ merchant", not "a person or a merchant and verified". Give each condition its own subject.
92
+ - Define a term by when it applies, not by a synonym: "'undetermined' when the name matches no
93
+ rule", not "'undetermined' means it cannot be determined".
85
94
 
86
95
  ## Words
87
96
 
@@ -49,9 +49,14 @@
49
49
  ## 结构与句子
50
50
 
51
51
  - 一个句子保持一个清晰主干,不连续堆叠条件、动作和例外。
52
+ - 写完整的句子,不写电报体:保留表达逻辑的词,包括条件(若……则、当……时)、因果(因为、所以)和转折(但)。省掉这些词,规则就成了要读者自己解码的标签。示例:`若窗口内无收款,则为 0`,而不是 `无收款为 0`;`付款人名称为空的收款不计入`,而不是 `空值不计`。
52
53
  - 标题说明用途或结论,不只写抽象名词。示例:`退单量在调价后翻倍`,而不是 `分析`。
53
54
  - 列表项保持相同层级、句式和信息密度;完整句式的列表项统一加句号。
54
55
  - 指代可能不清时,用具体名称替代「该」「其」「此」「上述」「相关」。
56
+ - 区间和阈值写明端点,并写明端点是否包含。示例:`北京时间 0:00(含)至 6:00(不含)`,而不是 `凌晨 0 点到 6 点之前`;`不低于 4,900 美元且低于 5,000 美元`,而不是 `比 5,000 美元低不到 2%`。
57
+ - 名词前的修饰语超过两层时拆开:先写主干,再把限定条件前置为状语或另起一句。示例:`非平台收款笔数,只计币种为美元、欧元或英镑且不经合作银行的收款`,而不是 `累计以美元、欧元或英镑收到、且不经合作银行渠道的非平台收款笔数`。
58
+ - 并列的条件逐个写全对象,不让后一个条件借用前一个条件的主语。「或」和「且」出现在同一个条件里时,用分句或列表写清每个连词管到哪里。示例:`客户已认证,且客户是个人或商户`,而不是 `客户是个人或商户且已认证`。
59
+ - 解释一个词时,写出什么情况下得到它,不用同义词绕回去。示例:`若名称不匹配任何规则,则为「无法判定」`,而不是 `「无法判定」表示无法判断`。
55
60
  - 否定范围必须明确,读者能判断禁止的是哪个动作。
56
61
  - 区分系统自动行为和人工操作。示例:`选择「保存」。系统随后写入配置并重新加载服务。`
57
62
 
@@ -73,7 +78,7 @@
73
78
  对齐 → 统一、确认一致;拉通 / 打通 → 连接;洞察 → 分析结论;兜底 → 写出失败后的具体保障;
74
79
  落盘 → 写入文件;透传 → 原样传给下游。
75
80
  - 以下词语依赖语境,不机械替换:场景、生态、体系、路径、触点、颗粒度、复盘、梳理、输出。
76
- - 不用装饰性连接词:值得注意的是、不难看出、综上所述、首先……其次……最后(非真实顺序时)。
81
+ - 不用装饰性连接词:值得注意的是、不难看出、综上所述、首先……其次……最后(非真实顺序时)。表达条件、因果、转折的连接词要保留(见[结构与句子](#结构与句子))。
77
82
 
78
83
  ## 标点与留白
79
84
 
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: polish-cn
3
3
  description: "Polish the Chinese wording of a finished document or report, with a script proving every number, date, identifier, link and protected term is unchanged; prefers a Chinese model and records which ran. Use for '中文润色' or as a report skill's last step. NOT for cutting or restructuring content (editorial-review) or translating (write-doc)."
4
- release-version: 0.36.0
4
+ release-version: 0.38.0
5
5
  ---
6
6
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
7
7
  # Polish Chinese
@@ -29,7 +29,7 @@ Set the model in the call's structured model argument. A model name inside the p
29
29
  nothing.
30
30
 
31
31
  - **Pi:** start a subagent with the provider-qualified id from Pi's model catalog, such as
32
- `model: "deepseek/deepseek-v4-flash"`, and read-only tools.
32
+ `model: "deepseek/deepseek-flash"`, and read-only tools.
33
33
  - **Codex CLI**, with a Chinese provider configured in `~/.codex/config.toml`:
34
34
  `codex exec -m <model id> --sandbox read-only --ephemeral --skip-git-repo-check -o reply.txt "<brief and input>"`.
35
35
  Otherwise use option 2.
@@ -2,7 +2,7 @@
2
2
  name: reg-parser
3
3
  version: 1.1.0
4
4
  description: "Parse regulatory/scheme documents into structured outputs: convert a regulation (AML, VARS, PCI-DSS, KYC, GDPR) into an audit-ready compliance checklist, or trace contract clauses to a mandate source. Suggest proactively when a regulation PDF accompanies a contract review or compliance task. NOT general summarization (doc-to-md), or writing the gap analysis or policy from the checklist (write-doc)."
5
- release-version: 0.36.0
5
+ release-version: 0.38.0
6
6
  ---
7
7
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
8
8
  # reg-parser
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: terminology
3
3
  description: "Build and keep a project's TERMINOLOGY.md: the preferred term per concept in English, 简体 and 繁體, and the terms to avoid. Use to set it up from the project's documents, when the user settles or corrects a term, or when another writing skill needs the format. NOT for writing documents (write-doc) or the code domain model (domain-modeling)."
4
- release-version: 0.36.0
4
+ release-version: 0.38.0
5
5
  ---
6
6
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
7
7
  # Terminology
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: write-doc
3
3
  description: "Write or edit a Markdown document in the project's house style, using the nearest WRITING.md and a document template (BRD, PRD, gap analysis, technical spec, integration guide, commercial proposal, compliance policy, risk operations procedure, or the project's own); English, Chinese or bilingual. NOT for learning a style from samples (distill-writing), audit reports from findings (report-writing), or WeChat articles (wechat-article-writer)."
4
- release-version: 0.36.0
4
+ release-version: 0.38.0
5
5
  ---
6
6
  **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
7
7
  # Write a document