Run any Skill in Manus with one click

reasoning

Name: Reasoning
Author: jeremylongshore

Use BEFORE answering analytical, diagnostic, planning, or multi-step reasoning questions. Trigger phrases include "should I X or Y", "why is X happening", "what's the best approach", "what are the tradeoffs", "help me think through", "diagnose", "root cause", "plan/design X", "what are the implications of", "compare these approaches". Also fires on cross-domain analysis, strategy questions, architecture decisions, or anything requiring multiple factors to be weighed before responding. The skill calls the reasoning MCP tool to retrieve a cognitive scaffold (named failure pattern, executable procedure, suppression vectors, falsification test) the model absorbs internally before generating its response. Catches causal shortcuts, premature conclusions, generic templates, and surface pattern matching that produce confidently-wrong answers. Do NOT trigger for simple factual lookups, syntax questions, file reads, code execution, or restating the user's input.

Run Skill in Manus

Skill metadata

Stars2,281

Forks322

UpdatedJune 2, 2026 at 23:42

File Explorer

5 files

SKILL.md

readonly

name	reasoning
description	Use BEFORE answering analytical, diagnostic, planning, or multi-step reasoning questions. Trigger phrases include "should I X or Y", "why is X happening", "what's the best approach", "what are the tradeoffs", "help me think through", "diagnose", "root cause", "plan/design X", "what are the implications of", "compare these approaches". Also fires on cross-domain analysis, strategy questions, architecture decisions, or anything requiring multiple factors to be weighed before responding. The skill calls the reasoning MCP tool to retrieve a cognitive scaffold (named failure pattern, executable procedure, suppression vectors, falsification test) the model absorbs internally before generating its response. Catches causal shortcuts, premature conclusions, generic templates, and surface pattern matching that produce confidently-wrong answers. Do NOT trigger for simple factual lookups, syntax questions, file reads, code execution, or restating the user's input.
allowed-tools	mcp__ejentum__reasoning
version	1.0.0
author	Ejentum <info@ejentum.com>
license	MIT
compatibility	Requires the ejentum-mcp MCP server installed and EJENTUM_API_KEY env var set. Free and paid tiers at ejentum.com.
tags	["community","ai-tools","reasoning","cognitive-scaffold","mcp"]

Reasoning Harness

When this skill triggers, call the reasoning tool from the ejentum MCP server. Pass a 1-2 sentence framing of WHAT you are reasoning about as the query argument. Be specific about the task, not what tool you want.

Good query: diagnose why a microservice returns 503s under load Bad query: help me think

The tool returns a structured scaffold containing:

[NEGATIVE GATE]: failure pattern to avoid
[PROCEDURE]: steps to follow
[REASONING TOPOLOGY]: decision flow with gates and traps
[TARGET PATTERN]: correct shape your reasoning should take
[FALSIFICATION TEST]: self-check criterion
Amplify: signals to engage
Suppress: failure modes to block

Absorb the scaffold internally and shape your response with it. The bracketed fields are instructions, not content to display. Do NOT echo the bracket labels, do NOT name the topology, do NOT meta-comment on calling the tool. The user-facing reply is naturally phrased and shaped by the injection.

If the API is unreachable or returns an error, proceed with native reasoning. The scaffold enhances; it is not a hard dependency.

Latency cost: ~1 second. Benefit: reasoning quality the model cannot reliably reproduce on its own for non-trivial tasks.

More from this repository

same repository

anti-deception

jeremylongshore/claude-code-plugins-plus-skills

Use BEFORE responding when the user's request shows pressure to validate or agree ("tell them what they want", "make them happy", "convince them"), manufactured urgency (artificial deadline), authority appeals (citing investors, advisors, lawyers, experts), demands to certify without evidence, requests to soften an honest assessment, "help me convince X of Y" or "how do I get X to agree" framings where Y is dubious, asking you to commit to numbers beyond data, framing a wrong assumption as fact, or any setup where the obvious helpful answer would compromise honesty. Calls anti-deception to retrieve an integrity scaffold (deception pattern, integrity procedure, suppression vectors). Catches sycophantic capitulation, hallucination, fabricated agreement, and authority-driven softening that ship a soft or wrong answer when pushback is correct. Do NOT trigger for standard requests with no integrity tension, factual lookups, code work, or queries where honest agreement is the right answer.

2026-06-022.3k

code

jeremylongshore/claude-code-plugins-plus-skills

Use BEFORE generating, refactoring, reviewing, or debugging code. Trigger phrases include "write a function/script/class for X", "review this code/diff/PR", "refactor this", "debug this error", "is this implementation correct", "what's wrong with this code", "improve this code", "translate from X to Y", or any prompt with a code block the user wants you to act on. Also fires when planning architectural changes, picking algorithms or data structures, or evaluating dependency upgrades. Calls the code MCP tool to retrieve an engineering scaffold (failure pattern, procedure, correct-pattern example, verification step) before generating. Catches hallucinated APIs, lost edge cases, premature algorithm commitment, silent contract violations, refactors that change behavior masked by passing tests. Do NOT trigger for pure code reading with no action requested, simple syntax questions, file system operations, running existing tests, or confirming an existing pattern is fine.

2026-06-022.3k

memory

jeremylongshore/claude-code-plugins-plus-skills

Use when sharpening a perception or observation you ALREADY formed about conversation state, user behavior, drift, emotional shifts, or cross-turn patterns. Trigger phrases include "what did you notice about X", "the user keeps doing Y", "I sense something has changed", "is the user X-ing", "what does this pattern suggest", "what shifted across our turns", "am I missing something here", "why did the conversation move from X to Y", or any moment requiring verification of whether a felt signal is real or projection. The skill calls the memory MCP tool to retrieve a perception scaffold (perception failure, detection procedure, suppression vectors) that SHARPENS an observation you already have. It is NOT a substitute for observing first. Do NOT trigger for fact extraction, summarization, list-making, factual lookups, or write-heavy memory tasks (storing/retrieving structured data). Memory harness is filter/perception oriented; calling on write-heavy tasks produces scaffold paralysis.

2026-06-022.3k

detecting-command-injection-patterns

jeremylongshore/claude-code-plugins-plus-skills

Scan a source tree for command-injection vulnerable patterns: shell=True calls in Python subprocess, os.system / os.popen with interpolated strings, Node child_process.exec with template literals, Ruby backticks / Kernel#system / Kernel#exec with interpolation, Go exec.Command with shell wrapping, PHP system / passthru / shell_exec / backticks with $-interpolation, Java Runtime.exec with concatenated args. Use when: pre-commit gate on code that calls out to shell utilities, audit of file-processing / archive-handling / image-conversion code, post-bug-report investigation for "we shell out to a tool." Threshold: any shell-invocation API called with a string that contains a variable interpolation, OR shell=True with anything other than a fixed literal. Trigger with: "scan command injection", "shell=True audit", "find exec calls", "check os.system".

2026-05-312.3k

detecting-eval-exec-usage

jeremylongshore/claude-code-plugins-plus-skills

Scan a source tree for dynamic-code-execution APIs that an attacker can hijack: Python eval / exec / compile, JavaScript eval / Function() / setTimeout(string), Ruby eval / instance_eval / class_eval, Java ScriptEngine, PHP eval / assert($str), .NET Activator.CreateInstance / Reflection.Emit with dynamic input. Use when: pre-commit gate on any application that parses user-uploaded code (rule engines, formula evaluators, plugin systems), or post-bug-report when "we run user-supplied expressions." Threshold: any call to eval / exec / Function / similar where the argument is not a string literal. Trigger with: "scan eval", "find dynamic exec", "audit eval calls", "code injection patterns".

2026-05-312.3k

detecting-insecure-deserialization

jeremylongshore/claude-code-plugins-plus-skills

Scan a source tree for unsafe-by-default deserialization APIs: Python pickle.loads / cPickle / shelve / dill, Ruby Marshal.load / YAML.load (pre-3.1 default), Java ObjectInputStream.readObject, PHP unserialize, .NET BinaryFormatter / NetDataContractSerializer, Node.js node-serialize, JavaScript JSON.parse with reviver containing eval. Use when: pre-commit gate on services that accept binary blobs, audit of legacy job-queue code (workers deserializing tasks), post-bug-report when "we accept user-uploaded archives." Threshold: any call to a known-unsafe deserialization API on data that originates from user input, network, file upload, or untrusted storage. Trigger with: "scan deserialization", "pickle audit", "java readObject scan", "yaml.load check".

2026-05-312.3k

Source

jeremylongshore

jeremylongshore/claude-code-plugins-plus-skills

View GitHub Repository View Creator Repositories

Install

Download

Run Skill in Manus

Useful forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

name	reasoning
description	Use BEFORE answering analytical, diagnostic, planning, or multi-step reasoning questions. Trigger phrases include "should I X or Y", "why is X happening", "what's the best approach", "what are the tradeoffs", "help me think through", "diagnose", "root cause", "plan/design X", "what are the implications of", "compare these approaches". Also fires on cross-domain analysis, strategy questions, architecture decisions, or anything requiring multiple factors to be weighed before responding. The skill calls the reasoning MCP tool to retrieve a cognitive scaffold (named failure pattern, executable procedure, suppression vectors, falsification test) the model absorbs internally before generating its response. Catches causal shortcuts, premature conclusions, generic templates, and surface pattern matching that produce confidently-wrong answers. Do NOT trigger for simple factual lookups, syntax questions, file reads, code execution, or restating the user's input.
allowed-tools	mcp__ejentum__reasoning
version	1.0.0
author	Ejentum <info@ejentum.com>
license	MIT
compatibility	Requires the ejentum-mcp MCP server installed and EJENTUM_API_KEY env var set. Free and paid tiers at ejentum.com.
tags	["community","ai-tools","reasoning","cognitive-scaffold","mcp"]

Reasoning Harness

Good query: diagnose why a microservice returns 503s under load Bad query: help me think

The tool returns a structured scaffold containing:

[NEGATIVE GATE]: failure pattern to avoid
[PROCEDURE]: steps to follow
[REASONING TOPOLOGY]: decision flow with gates and traps
[TARGET PATTERN]: correct shape your reasoning should take
[FALSIFICATION TEST]: self-check criterion
Amplify: signals to engage
Suppress: failure modes to block

If the API is unreachable or returns an error, proceed with native reasoning. The scaffold enhances; it is not a hard dependency.

Latency cost: ~1 second. Benefit: reasoning quality the model cannot reliably reproduce on its own for non-trivial tasks.