Skip to main content
在 Manus 中运行任何 Skill
一键导入
grammy-jiang
GitHub 创作者资料

grammy-jiang

按仓库查看 7 个 GitHub 仓库中的 99 个已收集 skills。

已收集 skills
99
仓库
7
更新
2026-07-12
仓库浏览

仓库与代表性 skills

applied-corpus-tools-and-textual-devices
技术写作员

Review the applied use of corpus tools and textual analysis — keyword, concordance, and collocation analysis, description of existing translations, and tracking of textual devices (theme dynamics, clausal and iconic linkage, deixis) — set against the commission's purpose and risk level. Use when concrete tooling or textual-device tracking is under review; corpus design choices go to corpus-design-and-methodology.

2026-07-12
chinese-prose-and-europeanization
技术写作员

Review Chinese target prose for Europeanized distortion — defending concision, flexible syntax, and rhythmic force, matching connectors to the actual relation, and preferring concrete subjects over abstract nominalizations. Use when a Chinese target text's Europeanization is under review; translationese used as a quality proxy goes to translation-universals-and-the-third-code.

2026-07-12
cognition-pragmatics-and-contrastive-evidence
其他高等院校教师

Review how cognitive and contrastive-pragmatic evidence is used — admitting process research only where it clarifies comprehension or transfer, treating verbal reports and neuroimaging as limited evidence, and triangulating pragmatic claims across data types. Use when a cognition or contrastive-pragmatics claim underlies a quality judgement; the descriptive-norm reconstruction it informs goes to descriptive-studies-and-translational-norms.

2026-07-12
corpus-design-and-methodology
其他高等院校教师

Review whether a corpus-based translation study is built to answer its question — corpus type (parallel / monolingual comparable / multilingual comparable), comparability, metadata, alignment, and frequency normalisation — before any difference is attributed to translation status. Use when a corpus design or corpus statistic is under review; universals interpretation goes to translation-universals-and-the-third-code, applied tooling to applied-corpus-tools-and-textual-devices.

2026-07-12
cultural-filtering-ideology-and-globalization
其他高等院校教师

Review quality where culture, ideology, English-as-a-lingua-franca, and globalization bear on the choices, grounding any power or ideology critique in detailed linguistic form and function first. Use when a cultural-filter, ideology, or ELF/globalization claim is under review; the overt/covert filtering judgement goes to overt-covert-translation-and-equivalence.

2026-07-12
descriptive-studies-and-translational-norms
其他高等院校教师

Review whether translated text is studied descriptively and target-orientedly — a reproducible method, norms reconstructed from recurrent corpus regularities, and an individual pattern attributed to a translator only after author style, source-language, and sociolect are ruled out. Use when a descriptive method or a translational-norm claim needs review; universals go to translation-universals-and-the-third-code.

2026-07-12
error-analysis-and-evaluation-discipline
其他高等院校教师

Review the discipline of the evaluation itself — overt errors classified separately from covert dimensional mismatches, impressionistic criteria rejected unless made operationally checkable, and evidence strength preserved. Use when evaluation criteria, an error typology, or a confidence claim need checking; the source-profile basis they weight against goes to overt-covert-translation-and-equivalence.

2026-07-12
genre-childrens-literature-and-accessibility
其他高等院校教师

Review quality where genre and audience accessibility govern the choices — connecting a text to its genre class and checking children's and stage texts against the function they must serve, with accessibility claims backed by quantifiable textual features. Use when a genre-fit or accessibility claim needs review; register detail goes to register-field-tenor-mode-analysis.

2026-07-12
当前展示该仓库 Top 8 / 84 个已收集 skills。
audit
软件质量保证分析师与测试员

Audit code against designs, specs, or bug reports; review patches; check readiness. Use when asked to: check if features or functions are fully implemented, audit against a design or architecture doc, review a patch or unified diff, resolve or investigate a bug report, run an operational review, or assess AI-readiness. Also use when the user says "check features", "audit implementation", "review this diff", "fix this bug", "investigate", or "is the architecture satisfied". ALWAYS invoke the llm-sca-tooling MCP server — never read docs and write checks manually, never substitute Python imports or external tools.

2026-05-17
fix
软件开发工程师

Fix code issues using the right approach for the problem type. Routes to the appropriate sub-workflow: SAST alert repair (bandit/ruff security findings), test-driven bug repair (write failing test first, then fix), or safe refactor (restructure without changing behaviour). Use when asked to fix a SAST/bandit finding, fix a bug, repair a defect, refactor, reorganize, clean up, simplify, extract functions, rename symbols, or reduce duplication. Also use when `make verify` reports a bandit or ruff `S*` alert, or a reproduction script exists for a bug.

2026-05-17
ship
软件开发工程师

Prepare code to ship: update a dependency, run an evaluation/benchmark, or cut a versioned release with full gating. Use when asked to update, bump, or upgrade a dependency version, when a CVE is reported in a dependency, when `pip-audit` flags a vulnerable package, when asked to run benchmarks or record an evaluation run, assess AI-readiness, or when asked to prepare a release, cut a release, bump a version for publication, or tag a release. Requires explicit human approval for git tag and publish (HC3 — destructive operation). Uses the llm-sca-tooling MCP server for readiness and drift checks.

2026-05-17
audit
软件质量保证分析师与测试员

Audit code against designs, specs, or bug reports; review patches; check readiness. Use when asked to: check if features or functions are fully implemented, audit against a design or architecture doc, review a patch or unified diff, resolve or investigate a bug report, run an operational review, or assess AI-readiness. Also use when the user says "check features", "audit implementation", "review this diff", "fix this bug", "investigate", or "is the architecture satisfied". ALWAYS invoke the llm-sca-tooling MCP server — never read docs and write checks manually, never substitute Python imports or external tools.

2026-05-17
fix
软件开发工程师

Fix code issues using the right approach for the problem type. Routes to the appropriate sub-workflow: SAST alert repair (bandit/ruff security findings), test-driven bug repair (write failing test first, then fix), or safe refactor (restructure without changing behaviour). Use when asked to fix a SAST/bandit finding, fix a bug, repair a defect, refactor, reorganize, clean up, simplify, extract functions, rename symbols, or reduce duplication. Also use when `make verify` reports a bandit or ruff `S*` alert, or a reproduction script exists for a bug.

2026-05-17
ship
软件开发工程师

Prepare code to ship: update a dependency, run an evaluation/benchmark, or cut a versioned release with full gating. Use when asked to update, bump, or upgrade a dependency version, when a CVE is reported in a dependency, when `pip-audit` flags a vulnerable package, when asked to run benchmarks or record an evaluation run, assess AI-readiness, or when asked to prepare a release, cut a release, bump a version for publication, or tag a release. Requires explicit human approval for git tag and publish (HC3 — destructive operation). Uses the llm-sca-tooling MCP server for readiness and drift checks.

2026-05-17
daily-ai-intelligence-implementer
软件开发工程师

Use when implementing/building/coding the Daily AI Intelligence pipeline — Phase A thin daily-briefing tickets, source adapters, ranking, validation. Do NOT use to run, poll, or generate a daily brief — use the daily-ai-intelligence skill for that.

2026-07-11
daily-ai-intelligence
软件开发工程师

Run the daily AI technical-intelligence briefing workflow. Polls governed registry sources (GitHub releases, RSS/Atom, Hacker News, Reddit, Bluesky, X, papers, video/audio, manual items), normalizes and deduplicates events, ranks with topic memory and explicit feedback, generates a validated daily Markdown brief, and optionally exports to Obsidian, builds hot-topic dossiers, records feedback, runs weekly trend synthesis, or compares ranked output across registries. Use when the user asks for a "daily AI brief", "AI tooling watch", "coding-agent update scan", "MCP/Copilot/Claude Code daily brief", "weekly AI tooling trend memo", "hot-topic dossier from a daily brief", a "weekly AI tooling synthesis", or to "rank/validate/export today's AI intelligence". Do NOT use for academic literature reviews, PDF download/conversion, citation-graph expansion, or paper-only synthesis (use the `research-pipeline` skill instead).

2026-07-11
research-pipeline
其他高等院校教师

End-to-end reproducible academic-paper research using the research-pipeline CLI and MCP server. Plans queries, searches arXiv/Google Scholar/Semantic Scholar/OpenAlex/DBLP/HuggingFace, screens with BM25, downloads and converts PDFs to Markdown, extracts evidence, summarizes, validates, and writes a human-readable, evidence-cited research report. Iterates up to 4 rounds to close academic and engineering gaps, and resumes on top of any prior same-topic report. Use when the user asks to "research", "find papers", "survey the literature", "do a literature review", "analyze arXiv papers", "build a research report", "screen papers", "summarize papers", "expand citations", "fill research gaps", or "resume a prior research report". Do NOT use for general web search, simple PDF-to-Markdown conversion (use `research-pipeline convert-file` directly), or requirements analysis (use the req-analysis skill).

2026-07-11
blueprint
项目管理专家

Convert a research synthesis report into an implementation-neutral product blueprint for product concept, users, workflow, product experience direction, logical architecture, MVP, evaluation, handoff, and next-stage routing. Use when the user has a research report and asks to "Create a blueprint from this research report", "Design the product based on this research", "Turn this research into a product design", "What should we build?", "Generate a product blueprint", "Convert the research to an MVP plan", "Define the product experience direction", "Define how users should experience the product", "Define user trust/control/review expectations", "What should we build next?", "Which design stages should we run next?", or "Recommend the next stages after the blueprint"; or after research-pipeline handover. Aliases: "product-blueprint", "research-blueprint", "research-to-product". Do NOT use for more research, tech stack, detailed UI/UX design or wireframes, user-story requirements, or single-paper explanation.

2026-07-10
已展示 7 / 7 个仓库
已展示全部仓库
grammy-jiang Agent Skills | SkillsMP