Loading...
Loading...
Found 2 Skills
Use this when the user explicitly requests to "verify/optimize in-text citations of the `{topic}_review.tex` review" or to "run check-review-alignment". Use the host AI's semantic understanding to verify each citation against the literature content one by one. **Only when fatal citation errors are found**, make minimal rewrites to the "sentences containing citations", and reuse the rendering script of `systematic-literature-review` to output PDF/Word (the script does not directly call the LLM API locally). Core principle: **Do not modify for the sake of modifying**. When it is uncertain whether it is a fatal error, keep the original content and issue a warning in the report. ⚠️ Not applicable in the following cases: - The user only wants to generate the main body of a systematic review (should use systematic-literature-review) - The user only wants to add/verify BibTeX entries (should use a dedicated bib management process)
Drive the real `10x` CLI (@przeprogramowani/10x-cli) end to end the way a learner does — login, list, get, sync, changelog, doctor — against a local fake delivery API with isolated config and project dirs, and capture stdout/stderr/exit codes, PTY screens and file-tree hashes as proof. Use after changing a command, the writer, conflict handling, auth or the API client, when unit tests pass but you need to see the shipped behaviour, or when asked to "verify", "run the CLI", "prove it works".