— No reviews yet
0 installs
13 views
0.0% view→install
Install
$ agentstack add skill-panjose-co-scientist-convergence-check ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Are you the author of Convergence Check? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claimAbout
convergence-check
Goal:
- Evaluate whether a hypothesis newly entered the current top-k set and update the convergence counter deterministically.
Inputs:
hypothesis_idprevious_top_k_idscurrent_top_k_ids- current convergence count
- caller-owned
state/EVOLUTION_STATE.json
Outputs:
ConvergenceCheckResult- updated convergence count
- when consumed by the evolution loop, updated
state/EVOLUTION_STATE.json
Context Loading:
- Open
skills/shared-references/schema-index.md. - Read
packages/agent_contracts/pipeline_control.pyand confirm the exactEvolutionStateContractshape before writingstate/EVOLUTION_STATE.json. - Treat the top-k sets as caller-supplied frontier inputs. This skill only evaluates the rule and updates the counter.
Execution Contract:
- This skill is deterministic and must not call an LLM.
- Use
from tools import evaluate_convergenceas the stable invocation surface. - The exported helper is implemented in
packages/agent_mechanics/convergence_check.py. - The helper signature is
evaluate_convergence(hypothesis_id, previous_top_k_ids, current_top_k_ids, current_convergence_count) -> ConvergenceCheckResult.
Execution Steps:
- Open
skills/shared-references/schema-index.md, then readpackages/agent_contracts/pipeline_control.pybefore writingstate/EVOLUTION_STATE.json. - Read the candidate
hypothesis_id, the previous and current top-k sets, and the current convergence count. - Call
tools.evaluate_convergence(hypothesis_id, previous_top_k_ids, current_top_k_ids, current_convergence_count). - Return the
ConvergenceCheckResultto the caller. - When used by the evolution loop, persist the returned
entered_top_kandconvergenceCountvalues intostate/EVOLUTION_STATE.json. - Validate any updated
state/EVOLUTION_STATE.jsonartifact before declaring completion.
Artifact Rules:
- The convergence rule is fixed: entering the top-k frontier resets the counter to zero; otherwise the counter increments by one.
- Do not fold additional stopping logic into this skill. Stop decisions belong to evolution state management and completion verification.
Completion Rule:
- This skill is complete only when the deterministic result has been produced and any caller-owned
state/EVOLUTION_STATE.jsonupdate matches that result exactly.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: panjose
- Source: panjose/Co-Scientist
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.