Skip to content
Back to skills

Threadify Agree Next Step

ASecurity

Prepare and review one explicit next step from an active buyer conversation. Use when the owner wants exact wording, destination, permission checks and a recorded result.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 29, 2026
ai-agentsnode

Works with

  • cli

Security analysis

A100/100

Scanned September 29, 2026

npx -y skills add lennoxsaint/Threadify-workflows --skill threadify-agree-next-step --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Threadify Agree Next Step?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Threadify Agree Next Step
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lennoxsaint-threadify-agree-next-step/badge)](https://www.skillsdirectory.com/skills/lennoxsaint-threadify-agree-next-step)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: threadify-agree-next-step
description: Prepare and review one explicit next step from an active buyer conversation. Use when the owner wants exact wording, destination, permission checks and a recorded result.
---

# Threadify Agree the Next Step

Read `references/threadify-001.md`, `references/workflow-manifest.json` and `references/workflow-readme.md` from this skill directory.

Start from the supplied conversation and confirmed offer. Prepare exactly one next step with its recipient, destination, text and any promised date. If offer relevance or the next step is still unknown, ask one useful question or return to `threadify-your-next-moves`.

Use the installed exact-release CLI at `node ~/.threadify-workflows/current/cli/bin/threadify-workflows.mjs conversations`; when `THREADIFY_WORKFLOWS_HOME` was set during installation, resolve the same path below that state root. In a source checkout, use `node bin/threadify-workflows.mjs conversations`. Keep state private. Run `review`, show the exact action and hash, and accept only `approve` or `reject` for that display. Keep recipient interest, channel permission and owner approval separate.

Before a host delivery tool or manual handoff, re-open the source and record the fresh inspection. Persist `attempt_pending` through `begin-attempt` before the host acts. Record `succeeded`, `confirmed_not_sent` or `unknown` only from the real result. Never infer approval from silence or replay an uncertain action.

If the tool is unsupported, provide the manual next-step artifact and keep delivery unverified until the owner supplies evidence. A native reminder can prompt review only after explicit opt-in; it cannot approve or send.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…