Home / lennoxsaint / threadify-workflows · GitHub

threadify-agree-next-step SKILL.md skillA

This file is byte-identical to the first copy the registry indexed, one of 3 indexed copies. Same content hash, so the same checks give both the same grade.

threadify-agree-next-step from lennoxsaint/threadify-workflows is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add lennoxsaint/threadify-workflows/threadify-agree-next-step@git:20261014.88addd0

Pins git:20261014.88addd0 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: lennoxsaint/threadify-workflows
Path: plugins/openai/skills/threadify-agree-next-step/SKILL.md
Versions recorded: 2
Latest version: git:20261014.88addd0, committed Oct 14, 2026
First version recorded: Oct 9, 2026
Size: 1,961 bytes
Repository stars: 7
License: a license file GitHub does not identify

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.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# 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.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add lennoxsaint/threadify-workflows/threadify-agree-next-step@sha256:71d9f537ae5727c2

The line at the top of this page pins the label git:20261014.88addd0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_qeiru7on55c57ex3.svg)](https://markdownregistry.com/a/art_qeiru7on55c57ex3)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 2 versions of this file, between Oct 9, 2026 and Oct 14, 2026, about one every 4 days.

version	committed	commit	size	audit
git:20261014.88addd0 latest	2026-10-14	88addd0	1,961 B	A	view · diff
git:20261009.0dbb467	2026-10-09	0dbb467	1,705 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (1961 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

lennoxsaint/threadify-workflows · 7 stars · license a license file GitHub does not identify · pushed 2026-11-01 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_qeiru7on55c57ex3
GET https://markdownregistry.com/api/v1/resolve?ref=lennoxsaint/threadify-workflows/threadify-agree-next-step
GET https://markdownregistry.com/api/v1/blob/71d9f537ae5727c23a74c34f77e971abf4c976f5546f06bf21960dc483743b0b

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from lennoxsaint/threadify-workflows

threadify-30-day-viral-vault SKILL.md skill

lennoxsaint/threadify-workflows · plugins/claude/skills/threadify-30-day-viral-vault/SKILL.md · Plan 30 days and prepare six rights-cleared Threads posts daily while revealing only the next unresolved card. Use for…