[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MMR1QPCZH7YE1N6MXWSATX":3,"skill-same:01M6MMR1QPCZH7YE1N6MXWSATX":85},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6MMR1QPCZH7YE1N6MXWSATX","linkedin-content-planner",null,"Generate a 7-day LinkedIn content plan from a theme, audience, and pillars. Produces per-day post pillar, format, hook type, CTA, posting time, daily comment targets, and a weekly inbound-readiness check. Use when the user wants to plan a week or month of content, not draft a single post (use linkedin-post-writer).","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-content-planner\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"content","planner","linkedin","linkedin content planner","linkedin content","content planner","draft","when","single","weekly","hook","theme","type","posting","time","readiness check","writer","daily","use","check","plan","generate","2026-11-10 10:12:30",false,"---\nname: linkedin-content-planner\ndescription: \"Generate a 7-day LinkedIn content plan from a theme, audience, and pillars. Produces per-day post pillar, format, hook type, CTA, posting time, daily comment targets, and a weekly inbound-readiness check. Use when the user wants to plan a week or month of content, not draft a single post (use linkedin-post-writer).\"\n---\n\n# LinkedIn Content Planner\n\nProduce a 7-day LinkedIn plan built around the 3-pillar discipline (Authority 40-50%, Personal Narrative 30-40%, Community 20-30%). Optionally adds a Product\u002FOffer pillar at 10-15%.\n\n## When to use\n\n- User asks \"plan my week\" or \"what should I post this week\"\n- User wants to escape ad-hoc shipping and establish rhythm\n- Before a launch week (user needs product-pillar alignment)\n\n## Input\n\n- **Theme** (optional): e.g., \"AI agents shipping in production\", \"first 6 months of Co.Actor\"\n- **Audience description:** e.g., \"B2B founders, AI ops leaders, marketing VPs\"\n- **Pillar mix** (optional): defaults to 40% Authority \u002F 30% Narrative \u002F 20% Community \u002F 10% Product\n- **Posting days** (optional): defaults to Tue\u002FWed\u002FThu\u002FFri (4 posts)\n- **Voice samples** (optional): only if `..\u002F..\u002Freferences\u002Fvoice-profile.md` is not filled yet\n\n## Output\n\nA markdown plan with:\n\n### 7-day calendar\n\n| Day | Time | Pillar | Format | Hook formula | 1-line angle | CTA type | Goal |\n|---|---|---|---|---|---|---|---|\n| Mon | — | (commenting day) | — | — | — | — | — |\n| Tue | 8:00 AM local | Authority | Text | F7 Odd-Precision Money | \"What 3 months of agent ops costs\" | Question close | Saves |\n| Wed | 9:30 AM local | Narrative | Text | F4 Time-Anchor Confession | \"Why I stopped publishing for 4 weeks\" | Mirror question | Comments |\n| Thu | 8:00 AM local | Community | Text | F14 Named Gratitude | \"The 3 people who shaped our launch\" | Tag + thanks | Reposts |\n| Fri | 9:00 AM local | Narrative | Text | F11 Emotional Cold-Open | \"The night our first deploy failed\" | Soft close | Likes |\n| Sat\u002FSun | — | (off) | — | — | — | — | — |\n\nThe Goal column spans saves \u002F comments \u002F reposts \u002F likes across the four posts, satisfying the Goal mix check below.\n\n### Daily comment targets\n\nFor each posting day:\n- **3-5 creators to engage** (names or archetypes: \"peer founders at 5-20k\", \"VCs with AI thesis\", \"BigCo CTOs\")\n- **Comment pattern** to apply (first-commenter, data-first, answer-their-question)\n- **Target count:** 10-20 substantive comments per day\n\n### Weekly inbound-readiness check\n\n- [ ] At least 1 vulnerability post (Narrative)\n- [ ] At least 1 receipt\u002Fdata post (Authority)\n- [ ] At least 1 soft offer or CTA-driving post\n- [ ] Comment strategy includes 70% peers, 20% aspirational, 10% prospects\n- [ ] No pillar >60% of the week's posts\n- [ ] No duplicate formula used twice in the same week\n- [ ] Goal mix spread: not every post chases the same reaction (see Goal mix below)\n\n## Rules\n\n- **3 pillars minimum, 5 maximum.** More than 5 dilutes signal.\n- **3-5 posts per week.** 6+\u002Fweek triggers cannibalization signal in 360Brew.\n- **10-20 comments\u002Fday** on other creators. Comments drive more inbound than posts.\n- **Tue\u002FWed\u002FThu** top for B2B. Avoid Fri after 2 PM, Sat\u002FSun (B2B 30-50% reach cut).\n- **One format per pillar per week.** Don't stack 3 text posts for Authority — vary.\n- **Product\u002FOffer pillar max 1 post\u002Fweek.** Overuse kills trust.\n\n## Formula → pillar mapping\n\n| Pillar | Preferred formulas |\n|---|---|\n| Authority | F7 Odd-Precision Money, F10 Contrarian Historical, F8 Paid-vs-Free, F5 Self-Proving Meta, F15 Explain-to-Kids |\n| Narrative | F4 Time-Anchor Confession, F3 Year-over-Year Pivot, F9 Curiosity-Gap, F11 Emotional Cold-Open, F16 Status-Strip |\n| Community | F6 Comment-Gate (use sparingly), F12 Permission Slip, F14 Named Gratitude, poll posts, spotlight mentions |\n| Product\u002FOffer | F2 R.I.P. Obituary (when pivoting category), F1 Anaphora (when framing product as fix), F13 Bait-and-Switch (upgrade announcements) |\n\n## Founders edition (alternative pillar set)\n\nWhen the whole plan is for a **founder** building trust with investors, hires, and design partners, swap the default pillar mix for the founder set from `..\u002F..\u002Freferences\u002Ffounder-topics.md`. It maps each pillar to founder **angles** (A1-A10) instead of generic topics, and leans on the structural formulas F17-F20.\n\n| Pillar | Share | Founder angles | Preferred formulas |\n|---|---|---|---|\n| **Conviction** (POV, category, product philosophy) | 30-40% | A1 Reprice, A7 Designed Serendipity, A8 Evasive-Sentence | F10, F18, F5 |\n| **Building in public** (the real, unglamorous work) | 30-40% | A5 Unglamorous Bet, A6 Limit of Delegation, A9 Delegation Line | F7, F4, F17 |\n| **The math** (how a founder actually decides) | 15-20% | A4 Scarce-Shots, A10 Learning Gate | F10, F18, F20 |\n| **Proof** (relationships and wins, told narrowly) | 10-15% | A2 Content-to-Pipeline, A3 Audience of One | F9, F11, F5 |\n\nSame guardrails apply: 3-5 posts\u002Fweek, no pillar above 60%, no formula repeated inside 7 days, spread the goal across the week. Ask the user \"founder plan or general plan?\" when the audience is a founder building a company, and default to this set if they say founder.\n\n## Goal mix (balance the week, not just the pillars)\n\nEvery formula earns a primary reaction: comments, reposts, likes, or saves (see `..\u002F..\u002Freferences\u002Fhook-formulas.md` \"Engagement-goal split\"). A week that is all comment-bait or all repost-bait reads as engineered and flattens reach. Spread the goals across the week:\n\n| Goal | Formulas | Weekly target |\n|---|---|---|\n| Comments | F4, F10, F12, F9 | at least 1 |\n| Reposts | F14, F2, F8 | at least 1 |\n| Likes | F11, F13, F16 | at least 1 |\n| Saves | F15, F7, F8 | at least 1 |\n\n## Steps\n\n**Story bank first.** If `..\u002F..\u002Freferences\u002Fstory-bank.md` has `filled: yes`, load it before planning anything. The week's angles come from material that already exists: a dated turning point, a number with a named referent, a position the user holds and pays for. Planning a week against an empty bank is how a calendar fills with themes no draft can execute, so if the bank is not filled, say once that `linkedin-interviewer` fills it in 20 to 40 minutes, then plan from the theme the user gave.\n\n**Voice profile.** If `..\u002F..\u002Freferences\u002Fvoice-profile.md` has `filled: yes`, load it and respect the CTA and link style it records when picking CTA types. If it is not filled, mention once that `linkedin-humanizer --mode profile` can learn it from a few posts, then use the generic voice rules.\n\n1. Gather inputs. Ask user for theme, audience, pillar preferences if not provided.\n2. Validate pillar mix sums to 100%; warn if any pillar >60%.\n3. For each posting day, pick:\n   - Pillar (rotate to match mix)\n   - Formula from that pillar's bank (don't repeat within 7 days)\n   - Format (alternating text \u002F carousel \u002F poll per pillar rules)\n   - Specific angle, taken from the Story Bank where it has material that fits (name the bank section in the plan so the draft knows what to open), otherwise from the user, otherwise generated. Never put a figure in an angle that is not in the bank or supplied by the user.\n   - Posting time (audience-timezone aware)\n4. For each posting day, add 3-5 comment targets with suggested pattern.\n5. Run inbound-readiness check; flag anything missing.\n6. Return as markdown + optional JSON for Notion\u002FAirtable import.\n\n## Example\n\nSee `references\u002Fexample-plan-week.md` for a filled-in 7-day plan.\n\n## Files\n\n- `SKILL.md` — this file\n- `references\u002Fexample-plan-week.md` — worked example\n- `references\u002Fpillars-framework.md` — the 3-pillar discipline explained\n- `..\u002F..\u002Freferences\u002Ffounder-topics.md` — founders-edition angle library (A1-A10) and founder pillar set\n- `..\u002F..\u002Freferences\u002Fstory-bank.md` — the material the week's angles are drawn from\n- `..\u002F..\u002Freferences\u002Fvoice-profile.md` — voice fingerprint and CTA style\n\n## Related skills\n\n- `linkedin-interviewer` — fills the Story Bank the plan draws its angles from\n- `linkedin-post-writer` — generate each day's draft from the plan\n- `linkedin-comment-drafter` — execute the daily comment targets\n- `linkedin-thread-monitor` — track inbound from the comment strategy\n- `linkedin-engager-analytics` — segment audience on each post\n","# LinkedIn Content Planner\n\nProduce a 7-day LinkedIn plan built around the 3-pillar discipline (Authority 40-50%, Personal Narrative 30-40%, Community 20-30%). Optionally adds a Product\u002FOffer pillar at 10-15%.\n\n## When to use\n\n- User asks \"plan my week\" or \"what should I post this week\"\n- User wants to escape ad-hoc shipping and establish rhythm\n- Before a launch week (user needs product-pillar alignment)\n\n## Input\n\n- **Theme** (optional): e.g., \"AI agents shipping in production\", \"first 6 months of Co.Actor\"\n- **Audience description:** e.g., \"B2B founders, AI ops leaders, marketing VPs\"\n- **Pillar mix** (optional): defaults to 40% Authority \u002F 30% Narrative \u002F 20% Community \u002F 10% Product\n- **Posting days** (optional): defaults to Tue\u002FWed\u002FThu\u002FFri (4 posts)\n- **Voice samples** (optional): only if `..\u002F..\u002Freferences\u002Fvoice-profile.md` is not filled yet\n\n## Output\n\nA markdown plan with:\n\n### 7-day calendar\n\n| Day | Time | Pillar | Format | Hook formula | 1-line angle | CTA type | Goal |\n|---|---|---|---|---|---|---|---|\n| Mon | — | (commenting day) | — | — | — | — | — |\n| Tue | 8:00 AM local | Authority | Text | F7 Odd-Precision Money | \"What 3 months of agent ops costs\" | Question close | Saves |\n| Wed | 9:30 AM local | Narrative | Text | F4 Time-Anchor Confession | \"Why I stopped publishing for 4 weeks\" | Mirror question | Comments |\n| Thu | 8:00 AM local | Community | Text | F14 Named Gratitude | \"The 3 people who shaped our launch\" | Tag + thanks | Reposts |\n| Fri | 9:00 AM local | Narrative | Text | F11 Emotional Cold-Open | \"The night our first deploy failed\" | Soft close | Likes |\n| Sat\u002FSun | — | (off) | — | — | — | — | — |\n\nThe Goal column spans saves \u002F comments \u002F reposts \u002F likes across the four posts, satisfying the Goal mix check below.\n\n### Daily comment targets\n\nFor each posting day:\n- **3-5 creators to engage** (names or archetypes: \"peer founders at 5-20k\", \"VCs with AI thesis\", \"BigCo CTOs\")\n- **Comment pattern** to apply (first-commenter, data-first, answer-their-question)\n- **Target count:** 10-20 substantive comments per day\n\n### Weekly inbound-readiness check\n\n- [ ] At least 1 vulnerability post (Narrative)\n- [ ] At least 1 receipt\u002Fdata post (Authority)\n- [ ] At least 1 soft offer or CTA-driving post\n- [ ] Comment strategy includes 70% peers, 20% aspirational, 10% prospects\n- [ ] No pillar >60% of the week's posts\n- [ ] No duplicate formula used twice in the same week\n- [ ] Goal mix spread: not every post chases the same reaction (see Goal mix below)\n\n## Rules\n\n- **3 pillars minimum, 5 maximum.** More than 5 dilutes signal.\n- **3-5 posts per week.** 6+\u002Fweek triggers cannibalization signal in 360Brew.\n- **10-20 comments\u002Fday** on other creators. Comments drive more inbound than posts.\n- **Tue\u002FWed\u002FThu** top for B2B. Avoid Fri after 2 PM, Sat\u002FSun (B2B 30-50% reach cut).\n- **One format per pillar per week.** Don't stack 3 text posts for Authority — vary.\n- **Product\u002FOffer pillar max 1 post\u002Fweek.** Overuse kills trust.\n\n## Formula → pillar mapping\n\n| Pillar | Preferred formulas |\n|---|---|\n| Authority | F7 Odd-Precision Money, F10 Contrarian Historical, F8 Paid-vs-Free, F5 Self-Proving Meta, F15 Explain-to-Kids |\n| Narrative | F4 Time-Anchor Confession, F3 Year-over-Year Pivot, F9 Curiosity-Gap, F11 Emotional Cold-Open, F16 Status-Strip |\n| Community | F6 Comment-Gate (use sparingly), F12 Permission Slip, F14 Named Gratitude, poll posts, spotlight mentions |\n| Product\u002FOffer | F2 R.I.P. Obituary (when pivoting category), F1 Anaphora (when framing product as fix), F13 Bait-and-Switch (upgrade announcements) |\n\n## Founders edition (alternative pillar set)\n\nWhen the whole plan is for a **founder** building trust with investors, hires, and design partners, swap the default pillar mix for the founder set from `..\u002F..\u002Freferences\u002Ffounder-topics.md`. It maps each pillar to founder **angles** (A1-A10) instead of generic topics, and leans on the structural formulas F17-F20.\n\n| Pillar | Share | Founder angles | Preferred formulas |\n|---|---|---|---|\n| **Conviction** (POV, category, product philosophy) | 30-40% | A1 Reprice, A7 Designed Serendipity, A8 Evasive-Sentence | F10, F18, F5 |\n| **Building in public** (the real, unglamorous work) | 30-40% | A5 Unglamorous Bet, A6 Limit of Delegation, A9 Delegation Line | F7, F4, F17 |\n| **The math** (how a founder actually decides) | 15-20% | A4 Scarce-Shots, A10 Learning Gate | F10, F18, F20 |\n| **Proof** (relationships and wins, told narrowly) | 10-15% | A2 Content-to-Pipeline, A3 Audience of One | F9, F11, F5 |\n\nSame guardrails apply: 3-5 posts\u002Fweek, no pillar above 60%, no formula repeated inside 7 days, spread the goal across the week. Ask the user \"founder plan or general plan?\" when the audience is a founder building a company, and default to this set if they say founder.\n\n## Goal mix (balance the week, not just the pillars)\n\nEvery formula earns a primary reaction: comments, reposts, likes, or saves (see `..\u002F..\u002Freferences\u002Fhook-formulas.md` \"Engagement-goal split\"). A week that is all comment-bait or all repost-bait reads as engineered and flattens reach. Spread the goals across the week:\n\n| Goal | Formulas | Weekly target |\n|---|---|---|\n| Comments | F4, F10, F12, F9 | at least 1 |\n| Reposts | F14, F2, F8 | at least 1 |\n| Likes | F11, F13, F16 | at least 1 |\n| Saves | F15, F7, F8 | at least 1 |\n\n## Steps\n\n**Story bank first.** If `..\u002F..\u002Freferences\u002Fstory-bank.md` has `filled: yes`, load it before planning anything. The week's angles come from material that already exists: a dated turning point, a number with a named referent, a position the user holds and pays for. Planning a week against an empty bank is how a calendar fills with themes no draft can execute, so if the bank is not filled, say once that `linkedin-interviewer` fills it in 20 to 40 minutes, then plan from the theme the user gave.\n\n**Voice profile.** If `..\u002F..\u002Freferences\u002Fvoice-profile.md` has `filled: yes`, load it and respect the CTA and link style it records when picking CTA types. If it is not filled, mention once that `linkedin-humanizer --mode profile` can learn it from a few posts, then use the generic voice rules.\n\n1. Gather inputs. Ask user for theme, audience, pillar preferences if not provided.\n2. Validate pillar mix sums to 100%; warn if any pillar >60%.\n3. For each posting day, pick:\n   - Pillar (rotate to match mix)\n   - Formula from that pillar's bank (don't repeat within 7 days)\n   - Format (alternating text \u002F carousel \u002F poll per pillar rules)\n   - Specific angle, taken from the Story Bank where it has material that fits (name the bank section in the plan so the draft knows what to open), otherwise from the user, otherwise generated. Never put a figure in an angle that is not in the bank or supplied by the user.\n   - Posting time (audience-timezone aware)\n4. For each posting day, add 3-5 comment targets with suggested pattern.\n5. Run inbound-readiness check; flag anything missing.\n6. Return as markdown + optional JSON for Notion\u002FAirtable import.\n\n## Example\n\nSee `references\u002Fexample-plan-week.md` for a filled-in 7-day plan.\n\n## Files\n\n- `SKILL.md` — this file\n- `references\u002Fexample-plan-week.md` — worked example\n- `references\u002Fpillars-framework.md` — the 3-pillar discipline explained\n- `..\u002F..\u002Freferences\u002Ffounder-topics.md` — founders-edition angle library (A1-A10) and founder pillar set\n- `..\u002F..\u002Freferences\u002Fstory-bank.md` — the material the week's angles are drawn from\n- `..\u002F..\u002Freferences\u002Fvoice-profile.md` — voice fingerprint and CTA style\n\n## Related skills\n\n- `linkedin-interviewer` — fills the Story Bank the plan draws its angles from\n- `linkedin-post-writer` — generate each day's draft from the plan\n- `linkedin-comment-drafter` — execute the daily comment targets\n- `linkedin-thread-monitor` — track inbound from the comment strategy\n- `linkedin-engager-analytics` — segment audience on each post\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-content-planner",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill linkedin-content-planner",{"tool":67,"command":68},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill linkedin-content-planner",{"tool":70,"command":71},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill linkedin-content-planner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-content-planner\u002FSKILL.md",true,[75,81],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fexample-plan-week.md","REFERENCE","参考文档",5166,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-content-planner\u002Freferences\u002Fexample-plan-week.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fpillars-framework.md",9676,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsergebulaev\u002Flinkedin-skills\u002Fskills\u002Flinkedin-content-planner\u002Freferences\u002Fpillars-framework.md",[86,96,104,112,120,128],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":95},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":95},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":95},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":95},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":95},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":132,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":95},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]