Update to Lightbringer
Snapshot Oct 2, 2026 · 00:15 UTC · version 5.0.0
Package or technical metadata updated
Package contents changed in 4 files: .codex-plugin/plugin.json, skills/patent-portfolio/SKILL.md, skills/patent-portfolio/references/assignee-identification.md, …. Open the file diff to inspect the edits.
Observed in package metadata. These changes alone do not establish a new customer-facing feature.
Package file
5b5b8cb5a72eb62fd19b531dfbe5d7d797f1781a67d1855f6e8641de23bc7dea
dbb6d54bdfca4c3ebacd2d5e2f310f9ca0996425667748600e249fb0dd5a5c6c
Package file
4045
4667
Package file
Not present
{"sha256":"fc965fadce16620a6f6bd0a334b7d699fee6fff5f7796ee3fd4d51cc2e5c1f43","size":4263}
Package file
Not present
{"sha256":"a04f15a45034add1ed824c820f1981cff75e8c0541cf81fa09b3cb7b80ff4193","size":2170}
Compare saved observations
Download comparison JSONChanged files
skills/patent-portfolio/SKILL.md →
skills/patent-portfolio/references/assignee-identification.md →
skills/patent-portfolio/references/assignee-identification.md
--- before +++ after @@ -0,0 +1,25 @@ +# Assignee identification + +Use this guidance when discovering a portfolio by company, applicant or assignee name. `search_public_patents` searches patent publications by assignee; it does not resolve company identities. + +## Choose names to search + +Start with the legal names supplied by the user. An organisation's display name or trading brand may differ from the names used in patent filings. Known publications and other available sources can help identify relevant filing names. + +Include supported spelling variants, transliterations and former names. Establish whether subsidiaries or acquired companies belong in the requested portfolio before expanding to them. Keep uncertain entities separate and clarify those that would materially change the import scope. + +Retain the names searched and the evidence for including them, so the same scope can be used for subsequent updates. + +## Search and select publications + +Pass one name at a time through the `assignee` field using simple text. The tool does not accept provider-specific query syntax. Follow the returned `nextPage`, even when a page contains no matches; note `truncated` or other coverage limits. + +Assess returned assignee values and source information against the intended company. Similar names can identify different entities, and filings can list historical or joint applicants. Use known publications or technical context to resolve ambiguity. Keep unsupported matches out of the import set. + +The user determines whether selected publications belong in their own portfolio or are third-party references. An applicant or assignee name in a publication does not, by itself, establish current ownership. + +## No matches or incomplete results + +If there are no matches, check supported name variants and report the names searched. Say that the search returned no matching publications; this does not establish that the company has no patents. Keep any broader discovery within the user's intended company scope. + +Distinguish an empty result from an incomplete search caused by a provider error or a coverage limit. Report the unfinished portion so the user can decide whether further discovery is needed.
Full technical diff · 5 changed fields
changed /files/.codex-plugin~1plugin.json/sha256
"5b5b8cb5a72eb62fd19b531dfbe5d7d797f1781a67d1855f6e8641de23bc7dea"
"dbb6d54bdfca4c3ebacd2d5e2f310f9ca0996425667748600e249fb0dd5a5c6c"
changed /files/.codex-plugin~1plugin.json/size
4045
4667
added /files/skills~1patent-portfolio~1SKILL.md
Field was absent
{
"sha256": "fc965fadce16620a6f6bd0a334b7d699fee6fff5f7796ee3fd4d51cc2e5c1f43",
"size": 4263
}added /files/skills~1patent-portfolio~1references~1assignee-identification.md
Field was absent
{
"sha256": "a04f15a45034add1ed824c820f1981cff75e8c0541cf81fa09b3cb7b80ff4193",
"size": 2170
}added /files/skills~1patent-portfolio~1references~1import-and-refresh.md
Field was absent
{
"sha256": "c30b18b8d3b82a8cbf1d1794515b9f9c714d4ab70c7fd12a90a6d56ee24b4748",
"size": 5206
}Full snapshot data
{
"files": {
".app.json": {
"sha256": "3eb781886accd85ef1a70d21535efd00007cf1b905ccd2a3137f412939ed2bb4",
"size": 127
},
".codex-plugin/plugin.json": {
"sha256": "dbb6d54bdfca4c3ebacd2d5e2f310f9ca0996425667748600e249fb0dd5a5c6c",
"size": 4667
},
"skills/innovation-capture/SKILL.md": {
"sha256": "3925b9a95f8e464d9435b2a9730d594eb94022f8f36a872b45985552006c991d",
"size": 5960
},
"skills/innovation-capture/references/idea-identification.md": {
"sha256": "b28d11de3dfa121e58bdb36edc2714139a11f70261eb6a1e0ec1dc19d93dbba3",
"size": 4979
},
"skills/innovation-capture/references/lightbringer-authoring.md": {
"sha256": "d8d9f8334b7954d36eff6ba5367ef2b55f4a274a0ca480c8077c2f7e5c07a7ac",
"size": 10831
},
"skills/innovation-capture/references/service-conduct.md": {
"sha256": "79b76d1463ec5a79b76adc7f0f4e62cd7e2911f28d9cd14556e22d85e1f54976",
"size": 930
},
"skills/innovation-capture/references/source-exploration.md": {
"sha256": "114c18451721c89df40991cde9e568fc8f6b1b32e86d82b177958f466abe55d9",
"size": 7733
},
"skills/innovation-capture/references/source-mining.md": {
"sha256": "add8fb86985fbc27824f8ed0cf6656a15f538e9c3d23b88372913881a7fbafbd",
"size": 9937
},
"skills/patent-portfolio/SKILL.md": {
"sha256": "fc965fadce16620a6f6bd0a334b7d699fee6fff5f7796ee3fd4d51cc2e5c1f43",
"size": 4263
},
"skills/patent-portfolio/references/assignee-identification.md": {
"sha256": "a04f15a45034add1ed824c820f1981cff75e8c0541cf81fa09b3cb7b80ff4193",
"size": 2170
},
"skills/patent-portfolio/references/import-and-refresh.md": {
"sha256": "c30b18b8d3b82a8cbf1d1794515b9f9c714d4ab70c7fd12a90a6d56ee24b4748",
"size": 5206
},
"skills/patent-preparation/SKILL.md": {
"sha256": "6482408e0446240a657ab3221adaaec9800debcc9c13f7abb980606a9ad47f26",
"size": 3638
},
"skills/patent-preparation/references/service-conduct.md": {
"sha256": "79b76d1463ec5a79b76adc7f0f4e62cd7e2911f28d9cd14556e22d85e1f54976",
"size": 930
},
"skills/patent-review/SKILL.md": {
"sha256": "69d85dc2f2304d98b6762603bc2219e7ee67f58ef776a91a5efbbac3a3842be5",
"size": 5838
},
"skills/patent-review/references/review-workflows.md": {
"sha256": "6b11d0c6759697d2ef13662141c7c64650def2ea61bd5063a6b74298b2c2479a",
"size": 5681
},
"skills/patent-review/references/service-conduct.md": {
"sha256": "79b76d1463ec5a79b76adc7f0f4e62cd7e2911f28d9cd14556e22d85e1f54976",
"size": 930
}
}
}SHA-256 of public snapshot: a6e6a4f47ff2f64689df99e869938e857ece8fba48f105730fa707bdf9a599d0