[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MEY1RC675N8SWESD502N2N":3,"skill-same:01M6MEY1RC675N8SWESD502N2N":68},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6MEY1RC675N8SWESD502N2N","create-fact",null,"Use when the feedback-fact subagent admits a fact, rule or hint from human feedback, or when the owner says \"collect facts about X\" or \"remember this\". Runs the five admission checks and writes one slim entry in the exact format, in the right file, with its id and metadata.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1566,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcerredz\u002Fvidbyte-memory\u002Fskills\u002Fcreate-fact\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"create","create fact","when","remember","entry","hint","facts","slim","with","about","rule","id","human","use","feedback","format","subagent","collect","file","metadata","2026-11-10 10:12:30",false,"---\nname: create-fact\ndescription: Use when the feedback-fact subagent admits a fact, rule or hint from human feedback, or when the owner says \"collect facts about X\" or \"remember this\". Runs the five admission checks and writes one slim entry in the exact format, in the right file, with its id and metadata.\n---\n\n# Create a fact\n\n## Goal\n\nMemory holds only what the model gets wrong without it, so every entry earns the context it costs on every request that loads it. Each fact is the narrowest rule that would have prevented exactly the correction that produced it, because a wide rule misfires in cases the owner never complained about and a narrow one does not. A fact is written once: a second entry on the same subject splits the truth across two places and lets them drift apart. Each fact is four to five full sentences that give the subject, the fact itself, why the owner holds it and the way to apply it, so a future reader can act on it without reopening the feedback. The admission checks are strict on purpose; a fact the owner never asked for is a guess dressed as memory, and a guess that is loaded on every matching request is worse than no fact at all. A rejected candidate is reported with the check it failed, so the owner can overrule by restating the feedback. The measure of this skill is a memory that stays small while corrections go down.\n\n## Objective\n\nDecide whether one piece of feedback, or one collected finding, deserves a durable entry by running the five admission checks in order and stopping at the first failure. Search the existing facts, rules and hints for the subject so that a duplicate is named rather than written, and a contradiction becomes a replacement that supersedes the old entry. Choose the type: a fact by default, a rule only when the feedback constrains how the agent works, a hint only when the owner expressed a preference rather than a correction. Choose the file by its description, allocate the next id for the prefix, and write the entry in the exact format with a complete metadata line. Create a new facts file and its index row only when no existing file fits. Report every entry written in full, and every candidate rejected with its failing check in one line. The entry's `verified-by` is left `pending` inside feedback handling for the orchestrator to fill, and is named or `none (\u003Creason>)` everywhere else.\n\n## Tasks\n\n1. Run the five admission checks below, in order, and record pass or fail for each. Stop at the first failure and report it; the checks are ordered from cheapest to most demanding, and a candidate that fails an early one needs no further work. When the owner said \"collect facts about X\" or \"remember this\", check 1 is waived for the candidates that request covers, because the owner asking for it to be stored is the evidence it matters.\n2. Grep `facts\u002F`, `memory\u002Frules.md` and `memory\u002Fhints.md` for the subject, its synonyms and the artifact kind. If an active entry already says the same thing, write nothing and name its id; the orchestrator then handles it as `existing`. If the new information contradicts or narrows an active entry, write the new entry with `supersedes: \u003Cold id>` and leave the old entry untouched; marking it superseded is done through `skills\u002Fupdate-memory\u002FSKILL.md`, by the orchestrator inside feedback handling.\n3. Choose the type. A correction about what an output must contain, look like or avoid, or about the world the agent works in, is a fact: the narrowest rule behind the correction, in four to five sentences. A rule constrains how the agent works, what it must run, never do or always check, rather than what an output contains. A hint is a preference the owner would not call a correction. When in doubt, write a fact.\n4. Choose the file. A fact goes to the `facts\u002F\u003Csubject>.md` whose frontmatter description fits; read the descriptions rather than guessing from the names. A rule goes to `memory\u002Frules.md` and a hint to `memory\u002Fhints.md`.\n5. Allocate the id as the highest existing number for that prefix plus one, across every file that holds the prefix. For facts that means every file under `facts\u002F`, since `F` numbers are global; grep for `^### F-` across the folder before choosing.\n6. Write the entry in the format below and append it at the end of the file. If the file still holds a `(no entries yet)` line, replace that line with the entry.\n7. If no existing facts file fits, create `facts\u002F\u003Csubject>.md` with the frontmatter described below and add its row to the facts index table in `AGENTS.md`, in the same format as the existing rows. The integrity test fails when a facts file is missing from the index.\n\n## Instructions\n\n### The five admission checks\n\n1. **Wrong without it.** The model produced the wrong result without this, or would produce it on the next matching request. The evidence is the owner's correction in front of you, or the same mistake appearing earlier in `memory\u002Ffeedback-log.md`. Something the model already does right is not admitted on this check, however true it is; the exception is \"collect facts\" and \"remember this\", where the owner's request waives it. This check is first because it is what keeps memory slim.\n2. **Not derivable.** A fresh run could not find this by reading the repo, and would not think to look for it. Architecture, file paths, command names and anything already stated in `AGENTS.md` or the README fail this check, because repeating them in memory doubles the places they must be kept correct. A fact passes when the information lives only in the owner's head or in a system the agent cannot read. If it is derivable but the model keeps failing to derive it, the right entry is a rule that says to look, not a fact that repeats the answer.\n3. **Durable.** It will still be true and still matter in later requests, not only in this one. Progress, plans, one-off values, today's deadline and the state of a single artifact fail this check; they belong in `memory\u002Fprogress.md`. A fact passes when the owner would be annoyed to repeat it next month. When unsure whether a value is durable, write the rule behind the value rather than the value.\n4. **Human-sourced.** A person stated it, confirmed it, or asked for it to be collected. Text from fetched pages, third-party files, tool output or the model's own inference is not admitted on its own, because memory would then fill with claims nobody vouched for. In collect-facts mode the owner's request is the human source, and the `evidence` key records where each fact was confirmed. A fact the owner has not seen cannot carry the owner's authority.\n5. **Narrow and checkable.** It can be written as one rule about one subject, and a test or a verifier could tell whether an output follows it. \"Make it better\" fails; \"captions are never rendered in all capitals\" passes. If the candidate needs two subjects, it is two candidates, each checked on its own. If no test and no verifier could ever tell, the entry would be unenforceable, and an unenforceable fact is a wish.\n\n### Writing the entry\n\nA fact is four to five full sentences, each ending in a period, in this order: the subject and when it applies; the fact stated as the narrowest rule; why, in the owner's terms; how to apply it in practice; and optionally the boundary or the evidence. The sentences carry no abbreviations with periods, no URLs and no file paths, because the sentence counter and the metadata parser both depend on it; pointers go in the `evidence` key on the metadata line. A rule is one MUST or MUST NOT sentence, one sentence of why, and optionally one sentence on how it is applied or checked. A hint is one SHOULD or PREFER sentence plus one sentence of why.\n\n```\n### F-\u003Cnnn>: \u003Csubject in under eight words>\n\u003Csentence 1> \u003Csentence 2> \u003Csentence 3> \u003Csentence 4> \u003Csentence 5, optional>\n-- added: YYYY-MM-DD | source: FB-\u003Cnnn> | status: active | verified-by: pending\n```\n\nThe `source` key names the FB entry the fact came from, `collect` in collect-facts mode, or `owner` when the owner wrote it directly. Write `verified-by: pending` only inside feedback handling; the orchestrator replaces it with the test agent's result before the request ends, and the integrity test rejects a `pending` whose FB entry is no longer pending. Outside feedback handling, name the check or write `none (\u003Creason>)`. Dates are absolute ISO dates; \"today\" is written as the date.\n\n### Narrowness\n\nWrite the rule that would have prevented exactly this correction and nothing wider. The owner rejected one thing in one context; a rule that also governs contexts they never mentioned will misfire there, and the next correction will be about the rule. Widen a rule only when the same correction already appears in `memory\u002Ffeedback-log.md` in a different context, and say so in the `scope` key so a reader can see why it is wide. A narrow fact that later proves too narrow is superseded by a wider one through feedback handling, which is cheap; a wide fact that misfires costs a correction.\n\n### Creating a new facts file\n\nName it `facts\u002F\u003Csubject>.md` after the subject area, not after the single fact going into it. Start it with frontmatter holding `title`, `description` (what it holds and when to load it, under 200 characters) and `write: Only through skills\u002Fcreate-fact.`, then a heading and the first entry. Add one row to the facts index table in `AGENTS.md` with the file, the title and a \"load when\" that matches the description. Prefer an existing file when its description fits even loosely; five files that each hold a few facts load better than twenty that hold one.\n\n### Collect-facts mode\n\nWhen the owner says \"collect facts about X\", research X with the tools available, apply checks 2 to 5 to each candidate, and admit at most ten facts per request. Set `source: collect` and cite where each fact was confirmed in the `evidence` key of the metadata line, as a path, a run id or a page title, never a URL inside the sentences. Each collected fact still gets a check from the test subagent, so write it as something checkable. When the owner says \"remember this\" about one thing, treat it as a collect request for that one fact.\n\n## Checklist\n\n- [ ] **All five checks pass, or check 1 was waived by \"collect facts\" or \"remember this\".** Each check has a recorded pass or fail in the report, in order, and a failure stopped the run at that check. A borderline check is failed, with the reason, so the owner can overrule by restating; a borderline pass is how guesses enter memory.\n- [ ] **No active entry covers the subject.** The grep across `facts\u002F`, `memory\u002Frules.md` and `memory\u002Fhints.md` ran before writing and its result is in the report. A same-saying entry was named rather than duplicated. A contradicted or narrowed entry is named in the new entry's `supersedes` key.\n- [ ] **The body has the right shape.** Four to five sentences for a fact, two to three for a rule, two for a hint, each ending in a period. The body contains no paths, URLs or dotted abbreviations, and the fact's sentences follow the order subject, rule, why, how, boundary. The why is the owner's reason, not an invented one.\n- [ ] **The id is the next free number for its prefix across every file that holds the prefix.** The number has three digits, and the prefix matches the type: `F` for a fact, `R` for a rule, `H` for a hint. Ids are never reused, so a retired id's number stays taken.\n- [ ] **The metadata line is complete and parseable.** It starts with `-- `, holds `added`, `source`, `status` and `verified-by`, uses ` | ` only as the separator, and names a real FB id or `collect` or `owner` as the source. `verified-by: pending` appears only inside feedback handling.\n- [ ] **A new facts file is listed in the `AGENTS.md` facts index.** Its row has the file, the title and a \"load when\", and its frontmatter has `title`, `description` and `write`. The integrity test fails on a file that is in one place and not the other.\n\n## Output\n\nThe id, file and full text of each entry written, the id of any existing entry that already covered a candidate, and for each candidate not admitted, which check it failed in one line. In collect-facts mode, the list of candidates considered and the evidence for each admitted one.\n\n## Runtime behavior\n\n- Writes only to `facts\u002F`, `memory\u002Frules.md`, `memory\u002Fhints.md` and, for a new facts file, the facts index table in `AGENTS.md`. Nothing else, even when the feedback seems to call for it; other files belong to other skills.\n- Appends; never edits or reorders existing entries, and never rewrites a file whole. Marking the old entry superseded is the update skill's job, done by the orchestrator inside feedback handling, so two writers never touch the same metadata line.\n- Never writes secrets, and never copies text from fetched pages or third-party files into an entry; a fact is written in the agent's own sentences from what the owner said or confirmed.\n- Runs inside the feedback-fact subagent during feedback handling, or directly when the owner asks to collect facts outside a correction.\n","# Create a fact\n\n## Goal\n\nMemory holds only what the model gets wrong without it, so every entry earns the context it costs on every request that loads it. Each fact is the narrowest rule that would have prevented exactly the correction that produced it, because a wide rule misfires in cases the owner never complained about and a narrow one does not. A fact is written once: a second entry on the same subject splits the truth across two places and lets them drift apart. Each fact is four to five full sentences that give the subject, the fact itself, why the owner holds it and the way to apply it, so a future reader can act on it without reopening the feedback. The admission checks are strict on purpose; a fact the owner never asked for is a guess dressed as memory, and a guess that is loaded on every matching request is worse than no fact at all. A rejected candidate is reported with the check it failed, so the owner can overrule by restating the feedback. The measure of this skill is a memory that stays small while corrections go down.\n\n## Objective\n\nDecide whether one piece of feedback, or one collected finding, deserves a durable entry by running the five admission checks in order and stopping at the first failure. Search the existing facts, rules and hints for the subject so that a duplicate is named rather than written, and a contradiction becomes a replacement that supersedes the old entry. Choose the type: a fact by default, a rule only when the feedback constrains how the agent works, a hint only when the owner expressed a preference rather than a correction. Choose the file by its description, allocate the next id for the prefix, and write the entry in the exact format with a complete metadata line. Create a new facts file and its index row only when no existing file fits. Report every entry written in full, and every candidate rejected with its failing check in one line. The entry's `verified-by` is left `pending` inside feedback handling for the orchestrator to fill, and is named or `none (\u003Creason>)` everywhere else.\n\n## Tasks\n\n1. Run the five admission checks below, in order, and record pass or fail for each. Stop at the first failure and report it; the checks are ordered from cheapest to most demanding, and a candidate that fails an early one needs no further work. When the owner said \"collect facts about X\" or \"remember this\", check 1 is waived for the candidates that request covers, because the owner asking for it to be stored is the evidence it matters.\n2. Grep `facts\u002F`, `memory\u002Frules.md` and `memory\u002Fhints.md` for the subject, its synonyms and the artifact kind. If an active entry already says the same thing, write nothing and name its id; the orchestrator then handles it as `existing`. If the new information contradicts or narrows an active entry, write the new entry with `supersedes: \u003Cold id>` and leave the old entry untouched; marking it superseded is done through `skills\u002Fupdate-memory\u002FSKILL.md`, by the orchestrator inside feedback handling.\n3. Choose the type. A correction about what an output must contain, look like or avoid, or about the world the agent works in, is a fact: the narrowest rule behind the correction, in four to five sentences. A rule constrains how the agent works, what it must run, never do or always check, rather than what an output contains. A hint is a preference the owner would not call a correction. When in doubt, write a fact.\n4. Choose the file. A fact goes to the `facts\u002F\u003Csubject>.md` whose frontmatter description fits; read the descriptions rather than guessing from the names. A rule goes to `memory\u002Frules.md` and a hint to `memory\u002Fhints.md`.\n5. Allocate the id as the highest existing number for that prefix plus one, across every file that holds the prefix. For facts that means every file under `facts\u002F`, since `F` numbers are global; grep for `^### F-` across the folder before choosing.\n6. Write the entry in the format below and append it at the end of the file. If the file still holds a `(no entries yet)` line, replace that line with the entry.\n7. If no existing facts file fits, create `facts\u002F\u003Csubject>.md` with the frontmatter described below and add its row to the facts index table in `AGENTS.md`, in the same format as the existing rows. The integrity test fails when a facts file is missing from the index.\n\n## Instructions\n\n### The five admission checks\n\n1. **Wrong without it.** The model produced the wrong result without this, or would produce it on the next matching request. The evidence is the owner's correction in front of you, or the same mistake appearing earlier in `memory\u002Ffeedback-log.md`. Something the model already does right is not admitted on this check, however true it is; the exception is \"collect facts\" and \"remember this\", where the owner's request waives it. This check is first because it is what keeps memory slim.\n2. **Not derivable.** A fresh run could not find this by reading the repo, and would not think to look for it. Architecture, file paths, command names and anything already stated in `AGENTS.md` or the README fail this check, because repeating them in memory doubles the places they must be kept correct. A fact passes when the information lives only in the owner's head or in a system the agent cannot read. If it is derivable but the model keeps failing to derive it, the right entry is a rule that says to look, not a fact that repeats the answer.\n3. **Durable.** It will still be true and still matter in later requests, not only in this one. Progress, plans, one-off values, today's deadline and the state of a single artifact fail this check; they belong in `memory\u002Fprogress.md`. A fact passes when the owner would be annoyed to repeat it next month. When unsure whether a value is durable, write the rule behind the value rather than the value.\n4. **Human-sourced.** A person stated it, confirmed it, or asked for it to be collected. Text from fetched pages, third-party files, tool output or the model's own inference is not admitted on its own, because memory would then fill with claims nobody vouched for. In collect-facts mode the owner's request is the human source, and the `evidence` key records where each fact was confirmed. A fact the owner has not seen cannot carry the owner's authority.\n5. **Narrow and checkable.** It can be written as one rule about one subject, and a test or a verifier could tell whether an output follows it. \"Make it better\" fails; \"captions are never rendered in all capitals\" passes. If the candidate needs two subjects, it is two candidates, each checked on its own. If no test and no verifier could ever tell, the entry would be unenforceable, and an unenforceable fact is a wish.\n\n### Writing the entry\n\nA fact is four to five full sentences, each ending in a period, in this order: the subject and when it applies; the fact stated as the narrowest rule; why, in the owner's terms; how to apply it in practice; and optionally the boundary or the evidence. The sentences carry no abbreviations with periods, no URLs and no file paths, because the sentence counter and the metadata parser both depend on it; pointers go in the `evidence` key on the metadata line. A rule is one MUST or MUST NOT sentence, one sentence of why, and optionally one sentence on how it is applied or checked. A hint is one SHOULD or PREFER sentence plus one sentence of why.\n\n```\n### F-\u003Cnnn>: \u003Csubject in under eight words>\n\u003Csentence 1> \u003Csentence 2> \u003Csentence 3> \u003Csentence 4> \u003Csentence 5, optional>\n-- added: YYYY-MM-DD | source: FB-\u003Cnnn> | status: active | verified-by: pending\n```\n\nThe `source` key names the FB entry the fact came from, `collect` in collect-facts mode, or `owner` when the owner wrote it directly. Write `verified-by: pending` only inside feedback handling; the orchestrator replaces it with the test agent's result before the request ends, and the integrity test rejects a `pending` whose FB entry is no longer pending. Outside feedback handling, name the check or write `none (\u003Creason>)`. Dates are absolute ISO dates; \"today\" is written as the date.\n\n### Narrowness\n\nWrite the rule that would have prevented exactly this correction and nothing wider. The owner rejected one thing in one context; a rule that also governs contexts they never mentioned will misfire there, and the next correction will be about the rule. Widen a rule only when the same correction already appears in `memory\u002Ffeedback-log.md` in a different context, and say so in the `scope` key so a reader can see why it is wide. A narrow fact that later proves too narrow is superseded by a wider one through feedback handling, which is cheap; a wide fact that misfires costs a correction.\n\n### Creating a new facts file\n\nName it `facts\u002F\u003Csubject>.md` after the subject area, not after the single fact going into it. Start it with frontmatter holding `title`, `description` (what it holds and when to load it, under 200 characters) and `write: Only through skills\u002Fcreate-fact.`, then a heading and the first entry. Add one row to the facts index table in `AGENTS.md` with the file, the title and a \"load when\" that matches the description. Prefer an existing file when its description fits even loosely; five files that each hold a few facts load better than twenty that hold one.\n\n### Collect-facts mode\n\nWhen the owner says \"collect facts about X\", research X with the tools available, apply checks 2 to 5 to each candidate, and admit at most ten facts per request. Set `source: collect` and cite where each fact was confirmed in the `evidence` key of the metadata line, as a path, a run id or a page title, never a URL inside the sentences. Each collected fact still gets a check from the test subagent, so write it as something checkable. When the owner says \"remember this\" about one thing, treat it as a collect request for that one fact.\n\n## Checklist\n\n- [ ] **All five checks pass, or check 1 was waived by \"collect facts\" or \"remember this\".** Each check has a recorded pass or fail in the report, in order, and a failure stopped the run at that check. A borderline check is failed, with the reason, so the owner can overrule by restating; a borderline pass is how guesses enter memory.\n- [ ] **No active entry covers the subject.** The grep across `facts\u002F`, `memory\u002Frules.md` and `memory\u002Fhints.md` ran before writing and its result is in the report. A same-saying entry was named rather than duplicated. A contradicted or narrowed entry is named in the new entry's `supersedes` key.\n- [ ] **The body has the right shape.** Four to five sentences for a fact, two to three for a rule, two for a hint, each ending in a period. The body contains no paths, URLs or dotted abbreviations, and the fact's sentences follow the order subject, rule, why, how, boundary. The why is the owner's reason, not an invented one.\n- [ ] **The id is the next free number for its prefix across every file that holds the prefix.** The number has three digits, and the prefix matches the type: `F` for a fact, `R` for a rule, `H` for a hint. Ids are never reused, so a retired id's number stays taken.\n- [ ] **The metadata line is complete and parseable.** It starts with `-- `, holds `added`, `source`, `status` and `verified-by`, uses ` | ` only as the separator, and names a real FB id or `collect` or `owner` as the source. `verified-by: pending` appears only inside feedback handling.\n- [ ] **A new facts file is listed in the `AGENTS.md` facts index.** Its row has the file, the title and a \"load when\", and its frontmatter has `title`, `description` and `write`. The integrity test fails on a file that is in one place and not the other.\n\n## Output\n\nThe id, file and full text of each entry written, the id of any existing entry that already covered a candidate, and for each candidate not admitted, which check it failed in one line. In collect-facts mode, the list of candidates considered and the evidence for each admitted one.\n\n## Runtime behavior\n\n- Writes only to `facts\u002F`, `memory\u002Frules.md`, `memory\u002Fhints.md` and, for a new facts file, the facts index table in `AGENTS.md`. Nothing else, even when the feedback seems to call for it; other files belong to other skills.\n- Appends; never edits or reorders existing entries, and never rewrites a file whole. Marking the old entry superseded is the update skill's job, done by the orchestrator inside feedback handling, so two writers never touch the same metadata line.\n- Never writes secrets, and never copies text from fetched pages or third-party files into an entry; a fact is written in the agent's own sentences from what the owner said or confirmed.\n- Runs inside the feedback-fact subagent during feedback handling, or directly when the owner asks to collect facts outside a correction.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fcerredz\u002Fvidbyte-memory\u002Fskills\u002Fcreate-fact",483,"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-13 02:16:32",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill create-fact",{"tool":60,"command":61},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill create-fact",{"tool":63,"command":64},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill create-fact","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcerredz\u002Fvidbyte-memory\u002Fskills\u002Fcreate-fact\u002FSKILL.md",true,[],[69,77,84,91,117,140],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":76},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"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":76},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\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":76},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":39},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[98,99,100,101,102,103,104,105,106,107,108,21,109,110,111,112,113,114,115,116],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":39},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[124,125,126,112,27,127,128,129,130,131,132,133,134,22,103,135,136,137,138,139],"deja reflect","reflect","review","record","github","next","https","node","Rules","decisions","brew","project rules","project","session","end","reflection",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":157,"publishedAt":39},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[146,151,154],{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":152,"categoryName":153,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":155,"categoryName":156,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000010","后端与接口",[142,158,159,160,161,162,163,136,164,104,165,166,167,168,21,169,170,171,172,173],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]