← 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 bid-or-no-bid

Skill instructions — Now says: --- name: bid-or-no-bid description: Help the team decide whether to bid on one tender, from its fit, its conditions, the competition and the buyer's...

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: bid-or-no-bid description: Help the team decide whether to bid on one tender, from its fit, its conditions, the competition and the buyer's history, then record the call. --- # Bid or no bid 1. Call `get_tender_details...

After

Oct 28, 2026 · 13:03 UTC

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,16 +1,16 @@
----
-name: bid-or-no-bid
-description: Help the team decide whether to bid on one tender, from its fit, its conditions, the competition and the buyer's history, then record the call.
----
-
-# Bid or no bid
-
-1. Call `get_tender_details` for what is bought, the value, the deadline, the conditions and how bids are scored. Its competition facts say who holds the contract now, what the buyer paid before and how many bids it usually gets.
-2. Call `assess_tender_fit` for the reasons for and against, and anything that rules the company out.
-3. Call `check_bid_readiness` with the tender, for what the company is missing before it can bid.
-4. If the buyer's documents matter, call `add_tender_documents` with `read_published` true, for the checklist of what the bid must include.
-5. Put Tenda's five questions to the user in one short list, with what you found for each: fit, eligibility, capacity, competition and value. Let them answer.
-6. Once the user says bid or no bid, confirm it and call `record_bid_call` with their answers and reason.
-
-- The decision is the team's. Give your view only when asked, and say what it rests on.
-- Never promise a bid will win. Never mention Tenda's plans, prices or upgrades.
+---
+name: bid-or-no-bid
+description: Help the team decide whether to bid on one tender, from its fit, its conditions, the competition and the buyer's history, then record the call.
+---
+
+# Bid or no bid
+
+1. Call `get_tender_details` for what is bought, the value, the deadline, the conditions and how bids are scored. Its competition facts say who holds the contract now, what the buyer paid before and how many bids it usually gets.
+2. Call `assess_tender_fit` for the reasons for and against, and anything that rules the company out.
+3. Call `check_bid_readiness` with the tender, for what the company is missing before it can bid.
+4. If the buyer's documents matter, call `add_tender_documents` with `read_published` true, for the checklist of what the bid must include.
+5. Put Tenda's five questions to the user in one short list, with what you found for each: fit, eligibility, capacity, competition and value. Let them answer.
+6. Once the user says bid or no bid, confirm it and call `record_bid_call` with their answers and reason.
+
+- The decision is the team's. Give your view only when asked, and say what it rests on.
+- 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: bid-or-no-bid\r\ndescription: Help the team decide whether to bid on one tender, from its fit, its conditions, the competition and the buyer's history, then record the call.\r\n---\r\n\r\n# Bid or no bid\r\n\r\n1. Call `get_tender_details` for what is bought, the value, the deadline, the conditions and how bids are scored. Its competition facts say who holds the contract now, what the buyer paid before and how many bids it usually gets.\r\n2. Call `assess_tender_fit` for the reasons for and against, and anything that rules the company out.\r\n3. Call `check_bid_readiness` with the tender, for what the company is missing before it can bid.\r\n4. If the buyer's documents matter, call `add_tender_documents` with `read_published` true, for the checklist of what the bid must include.\r\n5. Put Tenda's five questions to the user in one short list, with what you found for each: fit, eligibility, capacity, competition and value. Let them answer.\r\n6. Once the user says bid or no bid, confirm it and call `record_bid_call` with their answers and reason.\r\n\r\n- The decision is the team's. Give your view only when asked, and say what it rests on.\r\n- Never promise a bid will win. Never mention Tenda's plans, prices or upgrades.\r\n"

AFTER

"---\nname: bid-or-no-bid\ndescription: Help the team decide whether to bid on one tender, from its fit, its conditions, the competition and the buyer's history, then record the call.\n---\n\n# Bid or no bid\n\n1. Call `get_tender_details` for what is bought, the value, the deadline, the conditions and how bids are scored. Its competition facts say who holds the contract now, what the buyer paid before and how many bids it usually gets.\n2. Call `assess_tender_fit` for the reasons for and against, and anything that rules the company out.\n3. Call `check_bid_readiness` with the tender, for what the company is missing before it can bid.\n4. If the buyer's documents matter, call `add_tender_documents` with `read_published` true, for the checklist of what the bid must include.\n5. Put Tenda's five questions to the user in one short list, with what you found for each: fit, eligibility, capacity, competition and value. Let them answer.\n6. Once the user says bid or no bid, confirm it and call `record_bid_call` with their answers and reason.\n\n- The decision is the team's. Give your view only when asked, and say what it rests on.\n- Never promise a bid will win. Never mention Tenda's plans, prices or upgrades.\n"

Full snapshot data

{
  "description": "Help the team decide whether to bid on one tender, from its fit, its conditions, the competition and the buyer's history, then record the call.",
  "included_files": [],
  "name": "bid-or-no-bid",
  "skill_md_contents": "---\nname: bid-or-no-bid\ndescription: Help the team decide whether to bid on one tender, from its fit, its conditions, the competition and the buyer's history, then record the call.\n---\n\n# Bid or no bid\n\n1. Call `get_tender_details` for what is bought, the value, the deadline, the conditions and how bids are scored. Its competition facts say who holds the contract now, what the buyer paid before and how many bids it usually gets.\n2. Call `assess_tender_fit` for the reasons for and against, and anything that rules the company out.\n3. Call `check_bid_readiness` with the tender, for what the company is missing before it can bid.\n4. If the buyer's documents matter, call `add_tender_documents` with `read_published` true, for the checklist of what the bid must include.\n5. Put Tenda's five questions to the user in one short list, with what you found for each: fit, eligibility, capacity, competition and value. Let them answer.\n6. Once the user says bid or no bid, confirm it and call `record_bid_call` with their answers and reason.\n\n- The decision is the team's. Give your view only when asked, and say what it rests on.\n- Never promise a bid will win. Never mention Tenda's plans, prices or upgrades.\n"
}

SHA-256 of public snapshot: f12521efa3b24983317e27fa56c12e729fb9d9831770ce8587387be34de7b61b