[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AQFZ0GD0YMGW7CFWAEE60B":3,"skill-same:01M7AQFZ0GD0YMGW7CFWAEE60B":48},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7AQFZ0GD0YMGW7CFWAEE60B","okta-workflows-tables",null,"Use when working with Okta Workflows Tables (the built-in data store): Search Rows (searchRows2) being case-sensitive ('The search expression is case sensitive') with no 'starts with' for text; the hard 3,500-row return cap regardless of the Limit field (page with the 0-based Offset input); table hard limits (500,000 rows\u002Ftable, 64 columns\u002Ftable, 16 KB \u002F 16,000 chars per cell, 200 tables paid \u002F 100 free); the Where Expression JSON lhs\u002Fop\u002Fjoin\u002Frhs quirk when testing with variables; the no-native-upsert read-then-write race (Search Rows → If\u002FElse on Row ID empty → Create Row or Update Row, duplicate rows under concurrency, serialize with a concurrency=1 helper — labeled THEORY); and high-frequency table requests triggering throttling. Triggers on Search Rows, searchRows2, case-sensitive table search, 3500 rows, Offset pagination, Where Expression, upsert, Create Row \u002F Update Row race, table row\u002Fcolumn\u002Fcell limits, To Lower Case.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fokta-workflows\u002Fskills\u002Fokta-workflows-tables\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: okta-workflows-tables\ndescription: \"Use when working with Okta Workflows Tables (the built-in data store): Search Rows (searchRows2) being case-sensitive ('The search expression is case sensitive') with no 'starts with' for text; the hard 3,500-row return cap regardless of the Limit field (page with the 0-based Offset input); table hard limits (500,000 rows\u002Ftable, 64 columns\u002Ftable, 16 KB \u002F 16,000 chars per cell, 200 tables paid \u002F 100 free); the Where Expression JSON lhs\u002Fop\u002Fjoin\u002Frhs quirk when testing with variables; the no-native-upsert read-then-write race (Search Rows → If\u002FElse on Row ID empty → Create Row or Update Row, duplicate rows under concurrency, serialize with a concurrency=1 helper — labeled THEORY); and high-frequency table requests triggering throttling. Triggers on Search Rows, searchRows2, case-sensitive table search, 3500 rows, Offset pagination, Where Expression, upsert, Create Row \u002F Update Row race, table row\u002Fcolumn\u002Fcell limits, To Lower Case.\"\n---\n\n# Okta Workflows — Tables (Built-in Data Store) (§3)\n\nSix quirks. Normalize case before writing AND searching, and never assume Search Rows returns more\nthan 3,500 rows.\n\n## Quirk 3.1 — Search Rows (searchRows2) is case-sensitive\n\nThe Search Rows card documentation states plainly: \"The search expression is case sensitive.\" Numeric\nconditions are fine; text matching fails on case mismatch, and there is no \"starts with\" for text.\n\n- *Workaround:* Normalize case with a Text - To Lower Case card before writing AND before searching,\n  or pull all rows and use a List - Filter (Custom) helper flow to perform case-insensitive\u002Fstarts-with\n  matching.\n- *Sources:* Okta docs stash_searchrows2.htm; support.okta.com\n  searching-a-table-using-a-custom-filter-in-workflows; maxkatz.net 2024\u002F01\u002F19\n\n## Quirk 3.2 — Hard 3,500-row return cap regardless of Limit\n\n\"Regardless of the limit selected, the function card returns a maximum of 3,500 rows from the\nselected table\" (stash_searchrows2.htm). Confirmed independently by Max Katz \"Workflows Tips #36\"\n(maxkatz.net, 2022\u002F09\u002F09): \"If a filter or limit is not applied to the table search, a maximum of\n3,500 rows from the selected table will be read by the Search Rows function card.\" Critical for\nsync-reconciliation tables that can grow large.\n\n- *Workaround:* Page with the Offset input (0-based) in a recursive\u002Fpaginated helper flow, or design\n  tables to be queried by indexed key columns returning fewer than 3,500 rows.\n\n## Quirk 3.3 — Table hard limits\n\n500,000 rows\u002Ftable; 64 columns\u002Ftable; 16 KB (16,000 chars) per cell; 200 tables (paid) \u002F 100 (free).\n\"You can't add a row to a table after you've reached the limit.\"\n\n- *Source:* workflows-system-limits.htm\n\n## Quirk 3.4 — Where Expression JSON quirk when testing with variables\n\nWhen passing a variable into the Where Expression and testing the card, you must hand-edit the Where\nExpression JSON (lhs\u002Fop\u002Fjoin\u002Frhs structure) or the test returns wrong output. Example:\n`{\"expr\":[{\"lhs\":\"Country\",\"op\":\"=\",\"join\":\"AND\",\"rhs\":\"Brazil\"},{\"lhs\":\"Code\",\"op\":\"=\",\"join\":\"AND\",\"rhs\":\"BR\"}]}`.\n\n- *Source:* maxkatz.net 2023\u002F10\u002F25\n\n## Quirk 3.5 — No native upsert \u002F concurrent-write race risk (THEORY)\n\nThere is no atomic upsert; the documented pattern is Search Rows → If\u002FElse on Row ID empty → Create\nRow or Update Row. When multiple concurrent flow executions (e.g., many event-hook-triggered flows)\nrun this read-then-write against the same table\u002Fkey, there is a classic race window that can create\nduplicate rows. **This concurrency\u002Flocking risk is a plausible-but-not-explicitly-documented inference\nfrom the read-then-write pattern — label as THEORY.** Mitigation: funnel all table writes through a\nsingle-concurrency (`concurrency=1`) helper flow or a scheduled batch to serialize writes.\n\n- *Sources:* support.okta.com how-to-conditionally-update-a-table; upsert-example\n\n## Quirk 3.6 — High-frequency table requests trigger throttling\n\n\"Table requests\" is an explicit throttling resource: \"Flows with highly active event cards that make\nrequests through Tables function cards\" are called out as throttling-eligible.\n\n- *Source:* about-execution-limits.htm\n","# Okta Workflows — Tables (Built-in Data Store) (§3)\n\nSix quirks. Normalize case before writing AND searching, and never assume Search Rows returns more\nthan 3,500 rows.\n\n## Quirk 3.1 — Search Rows (searchRows2) is case-sensitive\n\nThe Search Rows card documentation states plainly: \"The search expression is case sensitive.\" Numeric\nconditions are fine; text matching fails on case mismatch, and there is no \"starts with\" for text.\n\n- *Workaround:* Normalize case with a Text - To Lower Case card before writing AND before searching,\n  or pull all rows and use a List - Filter (Custom) helper flow to perform case-insensitive\u002Fstarts-with\n  matching.\n- *Sources:* Okta docs stash_searchrows2.htm; support.okta.com\n  searching-a-table-using-a-custom-filter-in-workflows; maxkatz.net 2024\u002F01\u002F19\n\n## Quirk 3.2 — Hard 3,500-row return cap regardless of Limit\n\n\"Regardless of the limit selected, the function card returns a maximum of 3,500 rows from the\nselected table\" (stash_searchrows2.htm). Confirmed independently by Max Katz \"Workflows Tips #36\"\n(maxkatz.net, 2022\u002F09\u002F09): \"If a filter or limit is not applied to the table search, a maximum of\n3,500 rows from the selected table will be read by the Search Rows function card.\" Critical for\nsync-reconciliation tables that can grow large.\n\n- *Workaround:* Page with the Offset input (0-based) in a recursive\u002Fpaginated helper flow, or design\n  tables to be queried by indexed key columns returning fewer than 3,500 rows.\n\n## Quirk 3.3 — Table hard limits\n\n500,000 rows\u002Ftable; 64 columns\u002Ftable; 16 KB (16,000 chars) per cell; 200 tables (paid) \u002F 100 (free).\n\"You can't add a row to a table after you've reached the limit.\"\n\n- *Source:* workflows-system-limits.htm\n\n## Quirk 3.4 — Where Expression JSON quirk when testing with variables\n\nWhen passing a variable into the Where Expression and testing the card, you must hand-edit the Where\nExpression JSON (lhs\u002Fop\u002Fjoin\u002Frhs structure) or the test returns wrong output. Example:\n`{\"expr\":[{\"lhs\":\"Country\",\"op\":\"=\",\"join\":\"AND\",\"rhs\":\"Brazil\"},{\"lhs\":\"Code\",\"op\":\"=\",\"join\":\"AND\",\"rhs\":\"BR\"}]}`.\n\n- *Source:* maxkatz.net 2023\u002F10\u002F25\n\n## Quirk 3.5 — No native upsert \u002F concurrent-write race risk (THEORY)\n\nThere is no atomic upsert; the documented pattern is Search Rows → If\u002FElse on Row ID empty → Create\nRow or Update Row. When multiple concurrent flow executions (e.g., many event-hook-triggered flows)\nrun this read-then-write against the same table\u002Fkey, there is a classic race window that can create\nduplicate rows. **This concurrency\u002Flocking risk is a plausible-but-not-explicitly-documented inference\nfrom the read-then-write pattern — label as THEORY.** Mitigation: funnel all table writes through a\nsingle-concurrency (`concurrency=1`) helper flow or a scheduled batch to serialize writes.\n\n- *Sources:* support.okta.com how-to-conditionally-update-a-table; upsert-example\n\n## Quirk 3.6 — High-frequency table requests trigger throttling\n\n\"Table requests\" is an explicit throttling resource: \"Flows with highly active event cards that make\nrequests through Tables function cards\" are called out as throttling-eligible.\n\n- *Source:* about-execution-limits.htm\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fokta-workflows\u002Fskills\u002Fokta-workflows-tables",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill okta-workflows-tables",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill okta-workflows-tables",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill okta-workflows-tables","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fokta-workflows\u002Fskills\u002Fokta-workflows-tables\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]