---
name: Accint Solve
slug: accint-solve
category: AI Engineering
description: "Routes a goal through acc's scored-memory loop using acc_act(runtime='solve'). Deliberates on returned brain frames and submits proposals. Ideal for agentic workflows requiring structured decision-making."
github: "https://github.com/sickn33/agentic-awesome-skills/tree/main/plugins/agentic-awesome-skills-claude/skills/accint-solve"
language: Python
stars: 44097
forks: 6502
install: "git clone https://github.com/sickn33/agentic-awesome-skills"
added: 2026-07-19T06:53:18.380Z
last_synced: 2026-07-29T06:36:07.000Z
canonical_url: "https://dirskills.com/skills/accint-solve"
---

# Accint Solve

Routes a goal through acc's scored-memory loop using acc_act(runtime='solve'). Deliberates on returned brain frames and submits proposals. Ideal for agentic workflows requiring structured decision-making.

**Install:** `git clone https://github.com/sickn33/agentic-awesome-skills`

## README

# solve
## When to Use

Use this skill when you need route a goal through acc's scored-memory loop via acc_act(runtime="solve"); deliberate any returned brain_frame and submit via continue.


Routing sugar over the two MCP verbs — no logic lives here.

1. Call `acc_act(runtime="solve", input="<the goal>")`.
2. If the result is **final**: surface the answer, the `commitment` id, and the cited `[ids]`.
3. If the result is a **brain_frame**: it is YOUR deliberation turn — the frame is typed
   (which hole, what was retrieved, what is predicted). Reason over it, then submit via
   `acc_act(runtime="continue", input={"frame_id": ..., "submit_token": ..., "proposal_text": ...})`.
4. End `proposal_text` with `PREDICT: <0.00-1.00> <why>`; acc strips that line before
   the owner sees it and uses it to calibrate the Work Model against later outcomes.
5. Never leave a received frame unresolved; never solo-derive outside the loop.
6. Close the commitment honestly later with `acc_act(runtime="outcome", ...)`.

## Limitations

- Use this skill only when the task clearly matches its upstream source and local project context.
- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.