Agent Skills › meamaturinlove221/TuringResearch_plus

meamaturinlove221/TuringResearch_plus

GitHub

用于维护TulingResearch Plus的MCP命名空间契约和架构文档。在涉及相关模块、测试或发布门禁时触发,负责更新核心YAML契约、技术文档及账本记录,确保命名规范与代码一致性。

30 skills 141

Install All Skills

npx skills add meamaturinlove221/TuringResearch_plus --all -g -y
More Options

List skills in collection

npx skills add meamaturinlove221/TuringResearch_plus --list

Skills in Collection (30)

用于维护TulingResearch Plus的MCP命名空间契约和架构文档。在涉及相关模块、测试或发布门禁时触发,负责更新核心YAML契约、技术文档及账本记录,确保命名规范与代码一致性。
更新TulingResearch Plus架构文档 修改MCP命名空间契约 调整YAML合同文件
.agents/skills/tulingresearch-architecture-contracts/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-architecture-contracts -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-architecture-contracts",
    "description": "Use when updating TulingResearch Plus architecture docs, MCP namespaces, or YAML contracts."
}

TulingResearch Plus Skill: tulingresearch-architecture-contracts

Role

Maintain MCP namespace contracts and architecture documents for TulingResearch Plus.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-architecture-contracts or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • docs/architecture.md
  • docs/mcp-tools.md
  • contracts/

Related contracts

  • contracts/core_tools.yaml
  • contracts/pdf_markdown.yaml
  • contracts/fusion_workflows.yaml
  • contracts/vault_schema.yaml
  • contracts/artifact_schema.yaml
  • contracts/race_features.yaml
  • contracts/paper_pipeline.yaml
  • contracts/error_schema.yaml

Related lanes

  • lanes/01_architecture_contracts.md

Required tests

  • tests/contract/test_release_gate_contract.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
保护确定性缓存键、元数据、失败重试、预算门控及状态账本追加行为。适用于涉及所有者车道、相关合约、模块或发布门禁的变更,需更新文件并运行单元测试。
修改共享缓存或失败账本 调整 BudgetGate 或 StateLedger 基础结构 触及所有者车道及相关合约
.agents/skills/tulingresearch-cache-and-ledger/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-cache-and-ledger -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-cache-and-ledger",
    "description": "Use when changing shared cache, failure ledger, BudgetGate, or StateLedger foundations."
}

TulingResearch Plus Skill: tulingresearch-cache-and-ledger

Role

Protect deterministic cache keys, cache metadata, failure retries, budget gates, and state ledger append behavior.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-cache-and-ledger or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research/cache/
  • src/tuling_research_plus/budget/
  • src/tuling_research_plus/ledger/

Related contracts

  • contracts/core_tools.yaml
  • contracts/error_schema.yaml
  • contracts/artifact_schema.yaml

Related lanes

  • lanes/06_workflow_orchestration.md

Required tests

  • tests/unit/test_cache_keys.py
  • tests/unit/test_cache_manager.py
  • tests/unit/test_failure_ledger.py
  • tests/unit/test_budget_models.py
  • tests/unit/test_state_ledger.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
维护 TulingResearch Core MCP 工具循环,确保本地核心工具及轻量级服务封装。涉及相关模块、合约、测试及发布门禁的修改与文档更新。
用户请求命名 tulingresearch-core-reproduction 工作触及所有者车道、相关合约、模块、测试或发布门禁
.agents/skills/tulingresearch-core-reproduction/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-core-reproduction -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-core-reproduction",
    "description": "Use when maintaining the minimal TulingResearch Core MCP tool loop."
}

TulingResearch Plus Skill: tulingresearch-core-reproduction

Role

Maintain local-only Core tools and keep MCP wrappers thin over services.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-core-reproduction or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research/mcp_server.py
  • src/tuling_research/scholar/
  • src/tuling_research/web/
  • src/tuling_research/session/

Related contracts

  • contracts/core_tools.yaml
  • contracts/error_schema.yaml

Related lanes

  • lanes/02_core_reproduction.md

Required tests

  • tests/contract/test_core_health_check.py
  • tests/unit/test_paper_content_service.py
  • tests/unit/test_web_content_service.py
  • tests/unit/test_session_registry.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于维护TulingResearch Plus的营销活动运行时行为,包括策略、战术及SOP执行。负责管理质量门禁、检查点、产物、预算校验及工作流编排,确保代码、测试与文档的一致性。
涉及营销活动运行时维护 修改策略、战术或SOP相关模块 更新质量门禁或预算检查逻辑 变更工作流编排配置
.agents/skills/tulingresearch-fusion-campaign-engine/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-fusion-campaign-engine -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-fusion-campaign-engine",
    "description": "Use when maintaining Campaign -> Strategy -> Tactic -> SOP runtime behavior."
}

TulingResearch Plus Skill: tulingresearch-fusion-campaign-engine

Role

Maintain deterministic campaign runtime, quality gates, checkpoint hooks, artifacts, and budget checks.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-fusion-campaign-engine or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/campaign/
  • src/tuling_research_plus/subtask/

Related contracts

  • contracts/fusion_workflows.yaml
  • contracts/artifact_schema.yaml

Related lanes

  • lanes/06_workflow_orchestration.md

Required tests

  • tests/unit/test_campaign_runner.py
  • tests/unit/test_campaign_registry.py
  • tests/unit/test_subtask_models.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: workflow-required.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于维护TulingResearch Plus项目的上下文管理,包括初始化、检查点、恢复、索引及摘要行为。处理相关合约、模块、测试及发布门控,确保上下文文件可恢复并更新账本与文档。
需要维护上下文初始化或检查点时 涉及上下文恢复、索引或摘要逻辑变更时 修改相关合约、模块或测试用例时
.agents/skills/tulingresearch-fusion-context-management/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-fusion-context-management -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-fusion-context-management",
    "description": "Use when maintaining context init, checkpoint, recover, index, or summarize behavior."
}

TulingResearch Plus Skill: tulingresearch-fusion-context-management

Role

Maintain recoverable context files, checkpoints, index entries, artifacts, and evidence refs.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-fusion-context-management or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/context/

Related contracts

  • contracts/fusion_workflows.yaml
  • contracts/artifact_schema.yaml

Related lanes

  • lanes/05_vault_memory.md

Required tests

  • tests/unit/test_context_models.py
  • tests/unit/test_context_service.py
  • tests/unit/test_context_index.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于维护候选评分、排名、可行性评估及晋升决策的技能。适用于涉及所有者车道、相关契约、模块、测试或发布门禁的工作,负责更新相关文件、运行测试并同步账本状态。
需要维护候选评分或排名时 进行可行性评估或晋升决策时 修改相关契约、模块或测试文件时
.agents/skills/tulingresearch-fusion-convergence/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-fusion-convergence -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-fusion-convergence",
    "description": "Use when maintaining candidate scoring, ranking, feasibility assessment, and promotion decisions."
}

TulingResearch Plus Skill: tulingresearch-fusion-convergence

Role

Maintain ranked decision reports, sensitivity notes, feasibility checks, and promotion gates.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-fusion-convergence or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/convergence/

Related contracts

  • contracts/fusion_workflows.yaml

Related lanes

  • lanes/04_yogsoth_fusion.md

Required tests

  • tests/unit/test_candidate_scoring.py
  • tests/unit/test_pairwise_ranking.py
  • tests/unit/test_feasibility_assessment.py
  • tests/unit/test_portfolio_optimize.py
  • tests/unit/test_promotion_decide.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: workflow-required.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于维护TulingResearch Plus项目中确定性创意生成、形态矩阵及多样性筛选的Skill。适用于涉及相关模块、合约或测试的工作,确保输出通过测试并更新账本。
用户请求命名tulingresearch-fusion-creative-ideation 工作触及所有者车道、相关合约、模块、测试或发布门控
.agents/skills/tulingresearch-fusion-creative-ideation/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-fusion-creative-ideation -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-fusion-creative-ideation",
    "description": "Use when maintaining deterministic idea generation and quality-diversity filtering."
}

TulingResearch Plus Skill: tulingresearch-fusion-creative-ideation

Role

Maintain deterministic idea candidates, morphological matrices, and diversity gates.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-fusion-creative-ideation or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/ideation/

Related contracts

  • contracts/fusion_workflows.yaml

Related lanes

  • lanes/04_yogsoth_fusion.md

Required tests

  • tests/unit/test_idea_models.py
  • tests/unit/test_morphological_matrix.py
  • tests/unit/test_idea_diversity.py
  • tests/unit/test_idea_generation.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: workflow-required.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于维护基于证据的洞察输出和质量门禁,涵盖差距分析、假设验证、边界映射、敏感性探测及问题重构。需更新相关文件、测试及账本,确保符合命名规范且无需外部网络访问。
执行差距分析 生成洞察报告 绘制边界地图 进行敏感性探测 重新定义问题
.agents/skills/tulingresearch-fusion-deep-insight/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-fusion-deep-insight -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-fusion-deep-insight",
    "description": "Use when maintaining gap analysis, insight generation, boundary maps, sensitivity probes, or reformulation."
}

TulingResearch Plus Skill: tulingresearch-fusion-deep-insight

Role

Maintain evidence-backed insight outputs and quality gates for gaps, assumptions, boundaries, and problem changes.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-fusion-deep-insight or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/insight/

Related contracts

  • contracts/fusion_workflows.yaml

Related lanes

  • lanes/04_yogsoth_fusion.md

Required tests

  • tests/unit/test_gap_analysis.py
  • tests/unit/test_boundary_map.py
  • tests/unit/test_sensitivity_probe.py
  • tests/unit/test_problem_reformulation.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: workflow-required.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
维护TulingResearch Plus实验计划生成、约束条件、场景与实施计划及结果Schema。适用于涉及相关模块、测试或发布门控的工作,需更新文件、通过测试并同步账本。
用户请求命名包含 tulingresearch-fusion-experiment-execution 工作触及所有者车道、相关契约、模块、测试或发布门控
.agents/skills/tulingresearch-fusion-experiment-execution/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-fusion-experiment-execution -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-fusion-experiment-execution",
    "description": "Use when maintaining experiment design, constraints, scenarios, implementation plans, or result schemas."
}

TulingResearch Plus Skill: tulingresearch-fusion-experiment-execution

Role

Maintain ExperimentPlan generation, constraints, scenario plans, implementation plans, and result schemas.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-fusion-experiment-execution or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/experiment/

Related contracts

  • contracts/fusion_workflows.yaml

Related lanes

  • lanes/04_yogsoth_fusion.md

Required tests

  • tests/unit/test_experiment_models.py
  • tests/unit/test_experiment_design.py
  • tests/unit/test_constraint_analysis.py
  • tests/unit/test_scenario_plan.py
  • tests/unit/test_implementation_plan.py
  • tests/unit/test_result_schema.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: workflow-required.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
维护可证伪假设、操作化定义、研究问题及证据组合,执行FINER检查。涉及假说生成与验证时调用,更新相关文件、测试及账本,确保符合TulingResearch Plus规范。
用户请求包含 tulingresearch-fusion-hypothesis-formation 工作涉及所有者车道、相关契约、模块、测试或发布门禁
.agents/skills/tulingresearch-fusion-hypothesis-formation/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-fusion-hypothesis-formation -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-fusion-hypothesis-formation",
    "description": "Use when maintaining hypothesis generation, falsifiability, FINER checks, or hypothesis portfolios."
}

TulingResearch Plus Skill: tulingresearch-fusion-hypothesis-formation

Role

Maintain falsifiable hypotheses, operationalization, research questions, and evidence-backed portfolios.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-fusion-hypothesis-formation or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/hypothesis/

Related contracts

  • contracts/fusion_workflows.yaml

Related lanes

  • lanes/04_yogsoth_fusion.md

Required tests

  • tests/unit/test_hypothesis_models.py
  • tests/unit/test_gap_prioritization.py
  • tests/unit/test_falsifiability.py
  • tests/unit/test_finer.py
  • tests/unit/test_hypothesis_portfolio.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: workflow-required.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
维护TulingResearch Plus的文献调查工作流,涵盖策略管理、筛选、证据矩阵构建、差距提取及干跑导出。适用于涉及相关模块、合同或发布门禁的任务,确保测试通过并更新账本。
用户请求名称匹配 tulingresearch-fusion-literature-survey 任务触及所有者车道、相关合同、模块、测试或发布门禁
.agents/skills/tulingresearch-fusion-literature-survey/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-fusion-literature-survey -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-fusion-literature-survey",
    "description": "Use when maintaining depth-gated literature survey workflows."
}

TulingResearch Plus Skill: tulingresearch-fusion-literature-survey

Role

Maintain survey strategies, screening, evidence matrix, gap extraction, and dry-run export.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-fusion-literature-survey or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/survey/

Related contracts

  • contracts/fusion_workflows.yaml

Related lanes

  • lanes/04_yogsoth_fusion.md

Required tests

  • tests/unit/test_survey_models.py
  • tests/unit/test_survey_depth_gate.py
  • tests/unit/test_survey_strategies.py
  • tests/unit/test_evidence_matrix.py
  • tests/unit/test_gap_extractor.py
  • tests/workflow/test_literature_survey_dry_run.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于将模糊的研究意图转化为North Star研究简报和方向候选项。维护冷、温、热启动工作流,处理相关合约、模块、测试及发布门控,更新主账本并生成通过测试的文档。
用户请求命名包含 tulingresearch-fusion-north-star 涉及 owner lane、相关合约、模块、测试或发布门控的工作
.agents/skills/tulingresearch-fusion-north-star/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-fusion-north-star -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-fusion-north-star",
    "description": "Use when converting vague research intent into North Star research briefs and direction candidates."
}

TulingResearch Plus Skill: tulingresearch-fusion-north-star

Role

Maintain cold-start, warm-start, and hot-start North Star workflows with fake services.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-fusion-north-star or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/north_star/

Related contracts

  • contracts/fusion_workflows.yaml

Related lanes

  • lanes/04_yogsoth_fusion.md

Required tests

  • tests/unit/test_north_star_models.py
  • tests/unit/test_north_star_service.py
  • tests/workflow/test_north_star_dry_run.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: workflow-required.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于维护TulingResearch Plus语义图工作流,包括论文、引用、推荐及作者网络工具。通过适配器模式实现,无需真实API密钥,支持模拟测试与干跑,确保代码、合同、测试及账本的一致性更新。
涉及语义图模块的维护 需要运行无API依赖的适配器测试 更新引用或作者图谱相关功能
.agents/skills/tulingresearch-fusion-semantic-graph/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-fusion-semantic-graph -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-fusion-semantic-graph",
    "description": "Use when maintaining Semantic Graph paper, citation, recommendation, and author-network tools."
}

TulingResearch Plus Skill: tulingresearch-fusion-semantic-graph

Role

Maintain adapter-only semantic graph workflows with fake adapter tests and no API keys.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-fusion-semantic-graph or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/semantic_graph/

Related contracts

  • contracts/fusion_workflows.yaml

Related lanes

  • lanes/04_yogsoth_fusion.md

Required tests

  • tests/unit/test_semantic_graph_models.py
  • tests/unit/test_citation_graph.py
  • tests/unit/test_author_graph.py
  • tests/contract/test_graph_tools_contract.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于维护红队检查、辩论、事前分析、反事实推理及故障模式分析的压力测试报告。旨在标记无根据的声明、不可证伪的假设及薄弱的实验计划,确保相关合同、模块和发布门控的合规性。
进行红队检查或辩论 执行事前分析或反事实推理 开展故障模式分析 涉及TulingResearch Plus相关合同或模块的维护
.agents/skills/tulingresearch-fusion-stress-test/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-fusion-stress-test -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-fusion-stress-test",
    "description": "Use when maintaining red-team checks, debates, premortems, counterfactuals, or failure-mode analysis."
}

TulingResearch Plus Skill: tulingresearch-fusion-stress-test

Role

Maintain stress reports that flag unsupported claims, unfalsifiable hypotheses, and weak experiment plans.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-fusion-stress-test or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/stress/

Related contracts

  • contracts/fusion_workflows.yaml

Related lanes

  • lanes/04_yogsoth_fusion.md

Required tests

  • tests/unit/test_claim_red_team.py
  • tests/unit/test_hypothesis_debate.py
  • tests/unit/test_experiment_premortem.py
  • tests/unit/test_counterfactual_probe.py
  • tests/unit/test_stress_report.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: workflow-required.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于维护子任务运行时,包括角色模拟、确定性干跑输出、提示词管理及质量门禁。适用于涉及工作流编排、合约模块及测试的场景,确保无网络依赖并更新相关文档与账本。
维护 TaskProfile 或提示词渲染 执行 SubtaskRunner 干跑 检查子任务质量门禁 修改子任务运行相关合约或测试
.agents/skills/tulingresearch-fusion-subtask-runtime/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-fusion-subtask-runtime -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-fusion-subtask-runtime",
    "description": "Use when maintaining TaskProfile, prompt rendering, dry-run SubtaskRunner, or subtask quality gates."
}

TulingResearch Plus Skill: tulingresearch-fusion-subtask-runtime

Role

Maintain single-window role simulation, deterministic dry-run output, prompts, and quality checks.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-fusion-subtask-runtime or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/subtask/
  • docs/codex-multi-agent.md

Related contracts

  • contracts/fusion_workflows.yaml

Related lanes

  • lanes/06_workflow_orchestration.md

Required tests

  • tests/unit/test_subtask_runner.py
  • tests/unit/test_subtask_quality.py
  • tests/unit/test_subtask_models.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: workflow-required.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于维护TulingResearch Plus的本地证据库、图谱边、代码检查及研究工件摄入。涉及相关模块、测试及文档更新时需调用,确保测试通过并同步账本记录。
需要维护markdown证据库或BM25索引时 处理图谱边、代码检查或研究工件摄入时
.agents/skills/tulingresearch-fusion-wiki-vault/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-fusion-wiki-vault -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-fusion-wiki-vault",
    "description": "Use when maintaining the markdown vault, BM25-like index, graph edges, lint, or artifact ingestion."
}

TulingResearch Plus Skill: tulingresearch-fusion-wiki-vault

Role

Maintain local claim-evidence vault pages, graph edges, linting, search, and ResearchArtifact ingestion.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-fusion-wiki-vault or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/vault/
  • docs/vault.md

Related contracts

  • contracts/vault_schema.yaml
  • contracts/artifact_schema.yaml

Related lanes

  • lanes/05_vault_memory.md

Required tests

  • tests/unit/test_vault_models.py
  • tests/unit/test_vault_markdown_io.py
  • tests/unit/test_vault_graph.py
  • tests/unit/test_vault_lint.py
  • tests/unit/test_vault_artifact_ingestion.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
协调TulingResearch Plus多车道工作,确保合同、测试、文档和账本同步更新。适用于涉及核心模块或发布门控的任务,通过虚拟服务验证,严格遵循命名规范与隔离约束。
需要跨车道协调TulingResearch Plus工作 涉及所有者车道、相关合同、模块、测试或发布门控的变更
.agents/skills/tulingresearch-master-orchestrator/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-master-orchestrator -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-master-orchestrator",
    "description": "Use when coordinating TulingResearch Plus lane work across contracts, models, tests, and ledgers."
}

TulingResearch Plus Skill: tulingresearch-master-orchestrator

Role

Coordinate single-window TulingResearch Plus work across lanes and ensure every round updates contracts, tests, docs, and ledgers.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-master-orchestrator or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • lanes/
  • contracts/
  • docs/

Related contracts

  • contracts/core_tools.yaml
  • contracts/fusion_workflows.yaml
  • contracts/race_features.yaml
  • contracts/paper_pipeline.yaml

Related lanes

  • lanes/00_master_ledger.md

Required tests

  • tests/contract/test_release_gate_contract.py
  • tests/contract/test_skills_integrity.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于定义和维护TulingResearch Plus的文章块及文档流边界。负责确保ArticleBlock就绪、DocFlow图更新、缺失证据报告及实验报告草稿门控,涉及模型、契约、测试及账本文件的同步与验证。
需要定义或修改文章块和文档流边界时 工作触及所有者车道、相关契约、模块、测试或发布门控时
.agents/skills/tulingresearch-paper-docflow-article-blocks/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-paper-docflow-article-blocks -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-paper-docflow-article-blocks",
    "description": "Use when defining TulingResearch Plus article block and document flow boundaries."
}

TulingResearch Plus Skill: tulingresearch-paper-docflow-article-blocks

Role

Maintain ArticleBlock readiness, DocFlow graph, missing evidence reports, and ExperimentReport draft gate.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-paper-docflow-article-blocks or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/paper/models.py
  • src/tuling_research_plus/paper/docflow.py
  • paper/blocks/

Related contracts

  • contracts/paper_pipeline.yaml
  • contracts/artifact_schema.yaml

Related lanes

  • lanes/08_paper_pipeline.md

Required tests

  • tests/unit/test_article_block.py
  • tests/unit/test_docflow.py
  • tests/contract/test_paper_tools_contract.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于管理TulingResearch Plus论文图表资产流水线,维护图表注册表、标题生成及文件路径。适用于涉及相关模块、测试或发布门禁的工作,确保代码与文档同步并更新账本。
用户请求命名 tulingresearch-paper-figure-asset-pipeline 工作触及所有者车道、相关契约、模块、测试或发布门禁
.agents/skills/tulingresearch-paper-figure-asset-pipeline/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-paper-figure-asset-pipeline -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-paper-figure-asset-pipeline",
    "description": "Use when defining TulingResearch Plus paper figure and asset pipeline boundaries."
}

TulingResearch Plus Skill: tulingresearch-paper-figure-asset-pipeline

Role

Maintain FigureAsset registry, captions, stable filenames, ArticleBlock links, and PDF provenance gates.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-paper-figure-asset-pipeline or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/paper/figure_registry.py
  • src/tuling_research_plus/paper/caption_generator.py
  • paper/figures/
  • paper/captions/
  • paper/tables/

Related contracts

  • contracts/paper_pipeline.yaml

Related lanes

  • lanes/08_paper_pipeline.md

Required tests

  • tests/unit/test_figure_registry.py
  • tests/unit/test_caption_generator.py
  • tests/contract/test_paper_tools_contract.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于生成 TulingResearch Plus SOP 图骨架或 Mermaid 工作流图的技能。负责维护 SOP 模型、导出文件及契约,确保在相关模块变更时更新文档、测试和账本,并遵循严格的命名与隔离约束。
需要生成 SOP 图骨架或 Mermaid 工作流图时 工作涉及所有者车道、相关契约、模块、测试或发布门控时
.agents/skills/tulingresearch-paper-sop-graph-generator/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-paper-sop-graph-generator -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-paper-sop-graph-generator",
    "description": "Use when generating TulingResearch Plus SOP graph skeletons or Mermaid workflow diagrams."
}

TulingResearch Plus Skill: tulingresearch-paper-sop-graph-generator

Role

Maintain SOP graph models, Mermaid export, SOP Markdown, optional skill skeletons, and Codex prompts.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-paper-sop-graph-generator or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/sop/
  • sop_graphs/

Related contracts

  • contracts/paper_pipeline.yaml

Related lanes

  • lanes/08_paper_pipeline.md

Required tests

  • tests/unit/test_sop_graph.py
  • tests/unit/test_mermaid_export.py
  • tests/contract/test_paper_tools_contract.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
定义 TulingResearch Plus 论文写作与草稿工作流边界。管理草稿审查、证据缺失报告、章节就绪状态及防造假规则,负责 LaTeX 导出、相关代码文件更新、测试执行及账本记录维护。
涉及论文写作流程的模块或合同变更 需要生成或更新论文草稿及 LaTeX 导出 触发 tulingresearch-paper-writing-pipeline 指令
.agents/skills/tulingresearch-paper-writing-pipeline/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-paper-writing-pipeline -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-paper-writing-pipeline",
    "description": "Use when defining TulingResearch Plus paper writing and draft workflow boundaries."
}

TulingResearch Plus Skill: tulingresearch-paper-writing-pipeline

Role

Maintain paper draft gates, missing evidence reports, section readiness, no-fabrication rules, and LaTeX export.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-paper-writing-pipeline or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/paper/paper_writer.py
  • src/tuling_research_plus/paper/latex_export.py
  • paper/draft/

Related contracts

  • contracts/paper_pipeline.yaml

Related lanes

  • lanes/08_paper_pipeline.md

Required tests

  • tests/unit/test_paper_writer.py
  • tests/unit/test_paper_gate.py
  • tests/unit/test_latex_export.py
  • tests/contract/test_paper_tools_contract.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
维护TulingResearch Plus中本地PDF转Markdown的核心功能,支持检查、转换及缓存。无需外部API或重型OCR,通过固定测试确保发布安全,更新相关合约与账本记录。
用户请求涉及tulingresearch-pdf-markdown-core技能 工作触及PDF到Markdown转换的模块、测试或发布门控
.agents/skills/tulingresearch-pdf-markdown-core/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-pdf-markdown-core -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-pdf-markdown-core",
    "description": "Use when maintaining local PDF inspection, conversion, cache lookup, or Markdown content tools."
}

TulingResearch Plus Skill: tulingresearch-pdf-markdown-core

Role

Maintain fixture-safe local PDF to Markdown behavior without heavy OCR or real external APIs.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-pdf-markdown-core or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research/pdf/
  • docs/pdf_markdown.md

Related contracts

  • contracts/pdf_markdown.yaml
  • contracts/error_schema.yaml

Related lanes

  • lanes/03_pdf_markdown.md

Required tests

  • tests/unit/test_pdf_markdown_models.py
  • tests/unit/test_pdf_markdown_pipeline.py
  • tests/workflow/test_pdf_to_markdown_demo.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于验证 TulingResearch Plus 的测试、代码规范检查、类型检查、打包及发布就绪状态。确保文档、契约和测试与最新命名保持一致,并更新相关记录。
验证 TulingResearch Plus 测试用例 执行代码 linting 和类型检查 进行项目打包或发布前准备 检查发布就绪状态
.agents/skills/tulingresearch-qa-release/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-qa-release -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-qa-release",
    "description": "Use when validating TulingResearch Plus tests, linting, typing, packaging, or release readiness."
}

TulingResearch Plus Skill: tulingresearch-qa-release

Role

Run release gates and keep public release documentation, examples, contract tests, and workflow tests aligned.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-qa-release or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • docs/public-release-checklist.md
  • docs/public-readme-draft.md
  • docs/release-plan.md
  • examples/
  • tests/contract/
  • tests/workflow/

Related contracts

  • contracts/core_tools.yaml
  • contracts/fusion_workflows.yaml
  • contracts/race_features.yaml
  • contracts/paper_pipeline.yaml

Related lanes

  • lanes/09_qa_release.md

Required tests

  • tests/contract/test_release_gate_contract.py
  • tests/workflow/test_release_examples_fake_mode.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于将 TulingResearch Plus Race Mode 的发现映射到架构框中,维护16个架构框计划、依赖关系及 Mermaid 图表。当工作涉及所有者车道、相关契约或测试时使用。
用户请求命名匹配 tulingresearch-race-architecture-box-builder 工作触及所有者车道、相关契约、模块、测试或发布门禁
.agents/skills/tulingresearch-race-architecture-box-builder/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-race-architecture-box-builder -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-race-architecture-box-builder",
    "description": "Use when mapping TulingResearch Plus Race Mode findings into architecture boxes."
}

TulingResearch Plus Skill: tulingresearch-race-architecture-box-builder

Role

Maintain the 16-box architecture plan, dependencies, owner skills, and Mermaid graph output.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-race-architecture-box-builder or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/race/architecture_box.py
  • docs/architecture_16box.md

Related contracts

  • contracts/race_features.yaml

Related lanes

  • lanes/07_race_mode.md

Required tests

  • tests/unit/test_architecture_box.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于创建和验证P0/P1功能胶囊骨架,维护相关文件、契约、测试及文档。适用于涉及所有者车道、相关模块或发布门禁的工作场景。
创建或验证P0/P1 Feature Capsule骨架 工作涉及所有者车道、相关契约、模块、测试或发布门禁
.agents/skills/tulingresearch-race-feature-capsule-factory/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-race-feature-capsule-factory -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-race-feature-capsule-factory",
    "description": "Use when creating or validating P0\/P1 Feature Capsule skeletons."
}

TulingResearch Plus Skill: tulingresearch-race-feature-capsule-factory

Role

Maintain generated feature capsule files, contract, skill, tests, docs, and SOP graph skeletons.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-race-feature-capsule-factory or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/race/feature_capsule.py
  • race/feature_capsules/
  • docs/features/
  • sop_graphs/feature_graphs/

Related contracts

  • contracts/race_features.yaml

Related lanes

  • lanes/07_race_mode.md

Required tests

  • tests/unit/test_feature_capsule.py
  • tests/contract/test_race_tools_contract.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于在TulingResearch Plus项目中维护噪声文本到IdeaCard的确定性提取、TTS修正及动作门控。当涉及所有者车道、相关契约或测试时触发,确保输出符合发布标准并更新账本。
用户请求命名 tulingresearch-race-idea-radar 工作触及所有者车道、相关契约、模块或测试
.agents/skills/tulingresearch-race-idea-radar/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-race-idea-radar -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-race-idea-radar",
    "description": "Use when maintaining noisy text to IdeaCard extraction under Source Hygiene rules."
}

TulingResearch Plus Skill: tulingresearch-race-idea-radar

Role

Maintain deterministic IdeaCard extraction, TTS correction, uncertainty capture, and action gating.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-race-idea-radar or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/race/idea_radar.py
  • race/idea_cards/

Related contracts

  • contracts/race_features.yaml

Related lanes

  • lanes/07_race_mode.md

Required tests

  • tests/unit/test_idea_card.py
  • tests/unit/test_idea_radar.py
  • tests/contract/test_race_tools_contract.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于维护TulingResearch Plus中Race Mode的确定性加权优先级评分及源卫生降级规则。当工作涉及相关模块、合同或测试时使用,需更新指定文件并同步账本。
需要维护P0-P3优先级评分时 涉及Race Mode相关合同、模块或测试变更时 用户请求命名包含tulingresearch-race-priority-elevator时
.agents/skills/tulingresearch-race-priority-elevator/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-race-priority-elevator -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-race-priority-elevator",
    "description": "Use when maintaining P0\/P1\/P2\/P3 priority scoring and feature-capsule recommendations."
}

TulingResearch Plus Skill: tulingresearch-race-priority-elevator

Role

Maintain deterministic weighted Race Mode priority scoring and source-hygiene downgrade rules.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-race-priority-elevator or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/race/priority_elevator.py
  • race/priority_board.md

Related contracts

  • contracts/race_features.yaml

Related lanes

  • lanes/07_race_mode.md

Required tests

  • tests/unit/test_priority_elevator.py
  • tests/contract/test_race_tools_contract.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于维护 Race Mode 的源代码合规性,防止私有、泄露或许可证不兼容的代码进入。处理相关合同、模块、测试及发布门禁,确保符合 TulingResearch Plus 规范。
维护 Race Mode 的公共来源、许可证、NDA、私有或泄漏门禁 工作涉及所有者车道、相关合同、模块、测试或发布门禁
.agents/skills/tulingresearch-race-source-hygiene/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-race-source-hygiene -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-race-source-hygiene",
    "description": "Use when maintaining public-source, license, NDA, private, or leak gates for Race Mode."
}

TulingResearch Plus Skill: tulingresearch-race-source-hygiene

Role

Protect Race Mode from private, leaked, NDA, proprietary, or incompatible-license implementation sources.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-race-source-hygiene or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/race/source_hygiene.py
  • docs/race_mode.md

Related contracts

  • contracts/race_features.yaml

Related lanes

  • lanes/07_race_mode.md

Required tests

  • tests/unit/test_source_hygiene.py
  • tests/contract/test_race_tools_contract.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于监控 TulingResearch Plus Race Mode 的公开上游变更,执行快照差异分析、版本异常检测及生成 Watch 报告。在涉及相关模块、合约或发布门禁时触发,确保代码与文档同步更新并维持测试通过。
用户请求追踪上游变更 工作触及 Owner Lane 或相关合约/模块
.agents/skills/tulingresearch-race-upstream-watch/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-race-upstream-watch -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-race-upstream-watch",
    "description": "Use when tracking public upstream changes relevant to TulingResearch Plus Race Mode."
}

TulingResearch Plus Skill: tulingresearch-race-upstream-watch

Role

Maintain public-only upstream snapshot diffing, watch reports, version anomaly detection, and optional IdeaCards.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-race-upstream-watch or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • src/tuling_research_plus/race/upstream_watch.py
  • race/upstream_reports/

Related contracts

  • contracts/race_features.yaml

Related lanes

  • lanes/07_race_mode.md

Required tests

  • tests/unit/test_upstream_watch.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: release-critical.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.
用于将公共Yogsoth AI参考模式映射到TulingResearch Plus模块计划。确保复用边界和优先级映射准确,更新相关文档、合同及账本,保证测试通过且无外部依赖。
用户请求命名包含 tulingresearch-yogsoth-module-audit 工作涉及所有者车道、相关合同、模块、测试或发布门控
.agents/skills/tulingresearch-yogsoth-module-audit/SKILL.md
npx skills add meamaturinlove221/TuringResearch_plus --skill tulingresearch-yogsoth-module-audit -g -y
SKILL.md
Frontmatter
{
    "name": "tulingresearch-yogsoth-module-audit",
    "description": "Use when mapping public Yogsoth AI reference patterns into TulingResearch Plus module plans."
}

TulingResearch Plus Skill: tulingresearch-yogsoth-module-audit

Role

Keep public-reference reuse boundaries and module priority mapping accurate without copying external code.

When to use

Use this skill when work touches the owner lane, related contracts, modules, tests, or release gates listed below.

Inputs

  • User request naming tulingresearch-yogsoth-module-audit or the matching TulingResearch Plus lane.
  • Existing contracts, Pydantic models, tests, docs, and ledger entries.
  • Fake-service or dry-run fixtures when workflow behavior is involved.

Outputs

  • Updated TulingResearch Plus files in the listed required paths.
  • Passing focused tests and release-safe documentation updates.
  • Ledger updates in lanes/00_master_ledger.md and the owner lane.

Required files

  • docs/yogsoth-module-map.md
  • docs/fusion-priority.md
  • docs/reuse-boundary.md

Related contracts

  • contracts/fusion_workflows.yaml

Related lanes

  • lanes/04_yogsoth_fusion.md

Required tests

  • tests/contract/test_release_gate_contract.py

Rules / constraints

  • Project display name is TulingResearch Plus.
  • Core package is tuling_research and Plus package is tuling_research_plus.
  • MCP server name is tulingresearch-plus.
  • Skill names must use the tulingresearch- prefix.
  • Keep work inside TulingResearch/TulingResearch_plus.
  • Do not require real network access, external API keys, or live service calls in tests.
  • Preserve EvidenceRef, ResearchArtifact, BudgetGate, and StateLedger boundaries when relevant.
  • Use service protocols or adapters for external APIs.
  • Update the owner lane and lanes/00_master_ledger.md after meaningful changes.

Done criteria

  • Implementation status: locked.
  • Release requirement: planning-required.
  • Related tests pass or a release blocker is explicitly recorded.
  • Documentation and contracts remain aligned with current TulingResearch Plus naming.

ホーム - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-21 17:54
浙ICP备14020137号-1 $お客様$