界面已本地化;技能介绍与说明文档按所选语言由 AI 自动翻译,代码、命令、路径和专业术语保留原文,以原作者文档为准。
探索技能
开发与工程 · SKILL.md

not-human-search-mcp

not-human-search-mcp

【开发与工程】Implements intelligent not human search mcp with multi-factor skill selection, fallback chains, and adherence to the 5 Laws of Elegant Defense

独立 GitHub 快照 · 自动分类 · 以原作者文档为准

技能说明

GitHub

name: not-human-search-mcp compatibility: opencode completeness: 95 content-types:

  • guidance
  • examples
  • do-dont description: Implements intelligent not human search mcp with multi-factor skill selection, fallback chains, and adherence to the 5 Laws of Elegant Defense license: MIT maturity: stable metadata: domain: agent output-format: analysis related-skills: agent-confidence-based-selector, agent-task-routing role: orchestration scope: orchestration triggers: not-human-search-mcp, not human search mcp, how do i not-human-search-mcp, orchestrate not-human-search-mcp, automate not-human-search-mcp, agent not-human-search-mcp archetypes:
    • orchestration
    • strategic anti_triggers:
    • brainstorming
    • vague ideation
    • single-agent monolith response_profile: verbosity: medium directive_strength: high abstraction_level: tactical version: "1.0.0"

Not Human Search Mcp

Orchestrates intelligent skill selection and execution for not human search mcp workflows. Applies the 5 Laws of Elegant Defense to guide data naturally through the orchestration pipeline, preventing errors before they occur. Selects optimal skills based on multi-factor scoring including text similarity, historical performance, and system availability.

TL;DR Checklist

  • Parse all inputs at boundary before processing (Law 2)
  • Handle edge cases with early returns at function top (Law 1)
  • Fail immediately with descriptive errors on invalid states (Law 4)
  • Return new data structures, never mutate inputs (Law 3)
  • Implement minimum 2-level fallback chain for all skill executions
  • Log all skill selections with context for full audit trail
  • Validate skill metadata and dependencies before selection
  • Update confidence scores after each execution for learning

┌───────────────────────────────────────────────────────────────────────────────┐ │ Orchestration Flow │ └───────────────────────────────────────────────────────────────────────────────┘

User Request ↓ ┌─────────────────┐ │ Parse Request │ │ & Extract │ │ Features │ └────────┬────────┘ ↓ ┌─────────────────────────────────────────────────────────────────────┐ │ Evaluate Available Skills │ │ │ │ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │ │ │ Skill A │ │ Skill B │ │ Skill C │ │ │ │ - Match Score│ │ - Match Score│ │ - Match Score│ │ │ │ - Confidence │ │ - Confidence │ │ - Confidence │ │ │ │ - History │ │ - History │ │ - History │ │ │ └──────┬───────┘ └──────┬───────┘ └──────┬───────┘ │ │ │ │ │ │ │ └─────────────────┴─────────────────┘ │ │ ↓ │ │ Select Best Skill │ └─────────────────────────────────────────────────────────────────────┘ ↓ ┌─────────────────┐ │ Execute Skill │ └────────┬────────┘ ↓ ┌─────────────────┐ │ Handle Result │ └────────┬────────┘ ↓ ┌─────────────────────────────────────────────────────────────────────┐ │ Error Handling & Fallback │ │ │ │ Success? ────────► Return Result │ │ │ │ Fail? ────────┐ │ │ ↓ │ │ ┌──────────────────────────────────────────────────────────┐ │ │ │ Fallback Chain │ │ │ │ │ │ │ │ 1. Retry with adjusted parameters │ │ │ │ 2. Try Alternative Skill (if available) │ │ │ │ 3. Defer to Human Operator (if critical) │ │ │ │ 4. Log & Return Error │ │ │ └──────────────────────────────────────────────────────────┘ │ └─────────────────────────────────────────────────────────────────────┘

When to Use

Use this skill when:

  • Orchestrating multi-step workflows that require skill delegation
  • Implementing adaptive skill routing based on confidence scores
  • Building fallback mechanisms for failed skill executions
  • Creating intelligent task decomposition and parallel execution
  • Designing skill dependency graphs with automatic resolution
  • Implementing skill selection with historical performance weighting
  • Building agent systems that need to self-organize around tasks

When NOT to Use

Avoid this skill for:

  • Direct task execution without orchestration needs - use individual skills instead
  • High-frequency trading scenarios where latency must be minimized - the selection overhead may be prohibitive
  • Simple linear workflows without branching or fallback requirements
  • Cases where skill metadata is unavailable or unreliable

Core Workflow

  1. Parse and Analyze Request - Extract intent, entities, and constraints from user input. Checkpoint: All required parameters must be present and in valid format before proceeding.

  2. Score Available Skills - Calculate match scores using multi-factor algorithm:

    • Text similarity between request and skill triggers
    • Historical success rate for similar tasks
    • Skill availability and health status
    • Required dependencies and their availability

    Checkpoint: Skip to fallback if no skill scores above threshold.

  3. Select Optimal Skill - Choose skill with highest score that meets minimum confidence. Checkpoint: Verify skill has not been disabled or deprecated.

  4. Execute with Fallback - Run skill execution wrapped in retry and fallback logic. Checkpoint: Log all execution attempts for audit trail.

  5. Return or Fallback - Either return successful result or apply fallback chain:

    • Retry with adjusted parameters
    • Try alternative skill from related-skills
    • Defer to human operator for critical tasks

    Checkpoint: Record outcome with timing and confidence metadata.

Implementation Patterns

Pattern 1: Skill Selection Logic

def route_search_query(
    query: str,
    mcp_tools: List[Dict],
    query_config: Dict
) -> Dict:
    """Route a search query to the optimal MCP search tool.
    
    Analyzes query intent and constraints to select the best search backend.
    Implements Law 2: Parse inputs at boundary.
    """
    if not query or not query.strip():
        raise ValueError("Search query cannot be empty")
        
    # Extract query features for routing
    intent = _classify_intent(query)
    source_preference = query_config.get("preferred_source", "auto")
    
    candidates = []
    for tool in mcp_tools:
        if tool["type"] == "search" and tool.get("status") == "active":
            score = _calculate_search_match(intent, source_preference, tool)
            candidates.append({"tool": tool, "score": score})
            
    if not candidates:
        return {"error": "No active search tools available", "fallback": "cache"}
        
    # Sort by score and return best match with routing metadata
    candidates.sort(key=lambda x: x["score"], reverse=True)
    best = candidates[0]
    
    return {
        "selected_tool": best["tool"]["name"],
        "routing_metadata": {
            "intent": intent,
            "score": best["score"],
            "timestamp": time.time()
        }
    }

Pattern 2: Execution with Fallback

def execute_search_with_fallback(
    routing_result: Dict,
    query: str,
    search_config: Dict
) -> Dict:
    """Execute search with MCP tool and implement search-specific fallback chain.
    
    Implements Law 4: Fail fast, fail loud. Handles rate limits, timeouts, and empty results.
    Fallback: retry with expanded query -> fallback to cached index -> return partial results.
    """
    tool_name = routing_result["selected_tool"]
    max_retries = search_config.get("max_retries", 2)
    
    for attempt in range(max_retries + 1):
        try:
            # Call MCP search tool directly
            raw_results = _call_mcp_search_tool(tool_name, query)
            
            # Validate results (Law 3: Atomic Predictability)
            validated_results = _validate_search_results(raw_results)
            
            return {
                "success": True,
                "tool_used": tool_name,
                "results": validated_results,
                "attempts": attempt + 1,
                "latency_ms": time.time() * 1000
            }
            
        except MCPRateLimitError:
            if attempt < max_retries:
                time.sleep(2 ** attempt)  # Exponential backoff
                continue
            return _fallback_to_cached_index(query, search_config)
            
        except MCPTimeoutError:
            if attempt < max_retries:
                continue
            return _fallback_to_knowledge_base(query, search_config)
            
        except EmptyResultError:
            # Expand query and retry once
            if attempt == 0:
                query = _expand_query(query)
                continue
            return _fallback_to_partial_results(query, search_config)
            
    # All retries exhausted
    raise SearchExecutionError(f"Search failed for '{query}' after {max_retries + 1} attempts")

MUST DO

  • Always validate skill metadata before selection (Early Exit)
  • Implement fallback chain with at least 2 levels (Fallback Skill + Human)
  • Log all skill selections with full context for auditability
  • Return new data structures instead of mutating inputs (Atomic Predictability)
  • Fail immediately with descriptive errors on invalid states
  • Update confidence scores after each execution for adaptive routing
  • Reference code-philosophy (5 Laws of Elegant Defense) in all logic

MUST NOT DO

  • Select skills based on a single factor (e.g., only confidence score)
  • Disable fallback mechanisms "temporarily" - this creates fragile systems
  • Skip validation of skill dependencies before execution
  • Return partial results - either complete success or clear failure
  • Use magic numbers for confidence thresholds - make them configurable
  • Cache skill selections without considering context changes

TL;DR Checklist

  • Parse all inputs at boundary before processing (Law 2)
  • Handle edge cases with early returns at function top (Law 1)
  • Fail immediately with descriptive errors on invalid states (Law 4)
  • Return new data structures, never mutate inputs (Law 3)
  • Implement minimum 2-level fallback chain for all skill executions
  • Log all skill selections with context for full audit trail
  • Validate skill metadata and dependencies before selection
  • Update confidence scores after each execution for learning

TL;DR for Code Generation

  • Use guard clauses - return early on invalid input before doing work
  • Return simple types (dict, str, int, bool, list) - avoid complex nested objects
  • Cyclomatic complexity < 10 per function - split anything larger
  • Handle null/empty cases explicitly at function top (Early Exit)
  • Never mutate input parameters - return new dicts/objects
  • Fail fast with descriptive errors - don't try to "patch" bad data
  • Reference code-philosophy laws in comments for complex logic
  • Include timing and confidence metadata in all return values

Output Template

When applying this skill, produce:

  1. Selected Skills - List of skill names with confidence scores
  2. Selection Rationale - Why each skill was chosen (match score, history, availability)
  3. Execution Plan - Order of execution with dependencies
  4. Fallback Strategy - Which fallback skills will be tried and in what order
  5. Risk Assessment - Any potential failure points and their impact
  6. Timing Estimates - Expected latency including fallback scenarios

Related Skills

| Skill | Purpose | |



Constraints

MUST DO

  • Define clear input/output contracts for every step in the orchestration flow with explicit validation
  • Implement structured logging at each stage capturing context, inputs, outputs, timing, and errors
  • Build in fallback paths: if the primary strategy fails, degrade gracefully to a simpler approach
  • Validate all preconditions before starting — do not proceed if required resources or permissions are missing

MUST NOT DO

  • Do not create deep nesting of orchestration steps (>5 levels) — flatten workflows where possible
  • Avoid silent failure modes: every step must either succeed, fail explicitly, or escalate to a higher handler
  • Never use shared mutable state between parallel workflow branches — communicate via immutable messages only
  • Do not hardcode execution order when the dependency graph naturally determines it; derive order from explicit dependencies

Live References

Authoritative documentation links for this skill's domain. The model follows markdown links at load time to resolve external references and inline content.

我的收藏