@giftsofprometheus/cli 0.7.0 → 0.7.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
|
@@ -51,7 +51,11 @@ giftsofprometheus --json profile get # interests and curre
|
|
|
51
51
|
- Open a found transcript with `talks content <slug> --rec-id <recId>` from the `ask` response. To read around a passage, take `--outline` for the chapters, then `--from`/`--to` for the stretch you need instead of the whole transcript. Summarize positions of different speakers and give links with timecodes.
|
|
52
52
|
- A link to a moment is the talk `url` with `t` set to the second where the cited words start in the transcript segment, not the start of the `ask` passage. Keep the `recId` in every link.
|
|
53
53
|
- Each speaker has `organization` and `jobTitle` (`null` when unknown). Name a person's company only from these fields, never guess it. In a talk with several speakers, attribute a claim to a person only when the transcript makes clear who says it; otherwise attribute it to the talk. A company named in a title or a summary may be a customer or the subject of the talk, not the speaker's employer.
|
|
54
|
-
-
|
|
54
|
+
- Practice questions ("how to review / roll out / test / organize X", "how does the industry do X") are answered with how teams that run X in production do it, not with your own recipe:
|
|
55
|
+
- Queries for `ask` (the query and up to two `--q`): the core of the question in English; a first-person wording the way practitioners speak, such as `how we <do X> in production at our company`; lessons and failures, such as `lessons learned rolling out <X>`.
|
|
56
|
+
- Lead with companies that describe their own production practice; mark vendors presenting their product (the speaker works at the company that sells the tool) as vendors. Say plainly when the evidence is mostly vendor talks.
|
|
57
|
+
- Structure the answer by company: what they did, how it works, numbers from the talk, a link to the moment. End with a couple of lines on what they have in common, without "the right way" in your own voice.
|
|
58
|
+
- Do not apply this to "how to install / run / configure a specific tool", "what is X", or a search for a particular talk or speaker.
|
|
55
59
|
- If `ask` fails with code `passages_unavailable`, use `talks search`.
|
|
56
60
|
- Lists are paginated: check `totalPages` and pass `--page`.
|
|
57
61
|
- Search and use the returned `slug` or `id` for exact reads.
|
package/skills/history.json
CHANGED
|
@@ -68,5 +68,10 @@
|
|
|
68
68
|
"version": "0.7.0",
|
|
69
69
|
"hash": "ab66d3c17c52874a",
|
|
70
70
|
"description": "description: Find AI conference talks (AI Engineer, BAAI, Apsara and others) with Russian summaries, read their full transcripts, and manage the signed-in user's favorites, interests and personal feed through the giftsofprometheus CLI, and build a starting profile in the chat. Use when the user asks for talks, speakers or transcripts on an AI engineering topic, or wants to save, list or remove favorites on Gifts of Prometheus."
|
|
71
|
+
},
|
|
72
|
+
{
|
|
73
|
+
"version": "0.7.1",
|
|
74
|
+
"hash": "a16baed938e9e2a6",
|
|
75
|
+
"description": "description: Find AI conference talks (AI Engineer, BAAI, Apsara and others) with Russian summaries, read their full transcripts, and manage the signed-in user's favorites, interests and personal feed through the giftsofprometheus CLI, and build a starting profile in the chat. Use when the user asks for talks, speakers or transcripts on an AI engineering topic, or wants to save, list or remove favorites on Gifts of Prometheus."
|
|
71
76
|
}
|
|
72
77
|
]
|