← TendaCONTENT HISTORY

Update to Tenda

Snapshot Oct 28, 2026 · 13:03 UTC · version 1.1.0

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for write-and-check

Skill instructions — Now says: --- name: write-and-check description: Write a tender's bid answers with the person, answer by answer, and check each the way an evaluator would before it...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Tenda and check future changes in Following.

Up to 10 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Oct 24, 2026 · 13:45 UTC

--- name: write-and-check description: Write a tender's bid answers with the person, answer by answer, and check each the way an evaluator would before it goes in. --- # Write and check 1. Find the questions: call `add_tender_do...

After

Oct 28, 2026 · 13:03 UTC

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,14 +1,14 @@
----
-name: write-and-check
-description: Write a tender's bid answers with the person, answer by answer, and check each the way an evaluator would before it goes in.
----
-
-# Write and check
-
-1. Find the questions: call `add_tender_documents` with `read_published` true, or with the text the user shares. Use the scored questions, word limits and weights it returns.
-2. For each question, call `draft_bid_response` with the question, its limit and the user's own evidence, then show the draft.
-3. Call `review_bid_draft` on each answer the user is happy with, and fix what it marks down before moving on.
-4. If the user wants Tenda to draft the whole bid instead, call `start_bid_draft` and follow what it says about confirming first. Check progress with `get_bid_draft`, which also gives the Word file when it's ready.
-
-- Use only facts the user or their saved profile gives. Never make up case studies, numbers or accreditations.
-- A person must read every answer before it's submitted. Never promise a bid will win. Never mention Tenda's plans, prices or upgrades.
+---
+name: write-and-check
+description: Write a tender's bid answers with the person, answer by answer, and check each the way an evaluator would before it goes in.
+---
+
+# Write and check
+
+1. Find the questions: call `add_tender_documents` with `read_published` true, or with the text the user shares. Use the scored questions, word limits and weights it returns.
+2. For each question, call `draft_bid_response` with the question, its limit and the user's own evidence, then show the draft.
+3. Call `review_bid_draft` on each answer the user is happy with, and fix what it marks down before moving on.
+4. If the user wants Tenda to draft the whole bid instead, call `start_bid_draft` and follow what it says about confirming first. Check progress with `get_bid_draft`, which also gives the Word file when it's ready.
+
+- Use only facts the user or their saved profile gives. Never make up case studies, numbers or accreditations.
+- A person must read every answer before it's submitted. Never promise a bid will win. Never mention Tenda's plans, prices or upgrades.

Full technical diff · 1 changed fields

changed `/skill_md_contents`

BEFORE

"---\r\nname: write-and-check\r\ndescription: Write a tender's bid answers with the person, answer by answer, and check each the way an evaluator would before it goes in.\r\n---\r\n\r\n# Write and check\r\n\r\n1. Find the questions: call `add_tender_documents` with `read_published` true, or with the text the user shares. Use the scored questions, word limits and weights it returns.\r\n2. For each question, call `draft_bid_response` with the question, its limit and the user's own evidence, then show the draft.\r\n3. Call `review_bid_draft` on each answer the user is happy with, and fix what it marks down before moving on.\r\n4. If the user wants Tenda to draft the whole bid instead, call `start_bid_draft` and follow what it says about confirming first. Check progress with `get_bid_draft`, which also gives the Word file when it's ready.\r\n\r\n- Use only facts the user or their saved profile gives. Never make up case studies, numbers or accreditations.\r\n- A person must read every answer before it's submitted. Never promise a bid will win. Never mention Tenda's plans, prices or upgrades.\r\n"

AFTER

"---\nname: write-and-check\ndescription: Write a tender's bid answers with the person, answer by answer, and check each the way an evaluator would before it goes in.\n---\n\n# Write and check\n\n1. Find the questions: call `add_tender_documents` with `read_published` true, or with the text the user shares. Use the scored questions, word limits and weights it returns.\n2. For each question, call `draft_bid_response` with the question, its limit and the user's own evidence, then show the draft.\n3. Call `review_bid_draft` on each answer the user is happy with, and fix what it marks down before moving on.\n4. If the user wants Tenda to draft the whole bid instead, call `start_bid_draft` and follow what it says about confirming first. Check progress with `get_bid_draft`, which also gives the Word file when it's ready.\n\n- Use only facts the user or their saved profile gives. Never make up case studies, numbers or accreditations.\n- A person must read every answer before it's submitted. Never promise a bid will win. Never mention Tenda's plans, prices or upgrades.\n"

Full snapshot data

{
  "description": "Write a tender's bid answers with the person, answer by answer, and check each the way an evaluator would before it goes in.",
  "included_files": [],
  "name": "write-and-check",
  "skill_md_contents": "---\nname: write-and-check\ndescription: Write a tender's bid answers with the person, answer by answer, and check each the way an evaluator would before it goes in.\n---\n\n# Write and check\n\n1. Find the questions: call `add_tender_documents` with `read_published` true, or with the text the user shares. Use the scored questions, word limits and weights it returns.\n2. For each question, call `draft_bid_response` with the question, its limit and the user's own evidence, then show the draft.\n3. Call `review_bid_draft` on each answer the user is happy with, and fix what it marks down before moving on.\n4. If the user wants Tenda to draft the whole bid instead, call `start_bid_draft` and follow what it says about confirming first. Check progress with `get_bid_draft`, which also gives the Word file when it's ready.\n\n- Use only facts the user or their saved profile gives. Never make up case studies, numbers or accreditations.\n- A person must read every answer before it's submitted. Never promise a bid will win. Never mention Tenda's plans, prices or upgrades.\n"
}

SHA-256 of public snapshot: 53dbe53c160f4e14b63d348f48d02f7e39e5aa3450584603d527871446bba468