← 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 weekly-scan

Skill instructions — Now says: --- name: weekly-scan description: Go through this week's public tenders for the person's company, pick the few worth a look, and say what changed on the...

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: weekly-scan description: Go through this week's public tenders for the person's company, pick the few worth a look, and say what changed on the ones they follow. --- # Weekly scan 1. Call `get_tender_updates` for what ...

After

Oct 28, 2026 · 13:03 UTC

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,14 +1,15 @@
----
-name: weekly-scan
-description: Go through this week's public tenders for the person's company, pick the few worth a look, and say what changed on the ones they follow.
----
-
-# Weekly scan
-
-1. Call `get_tender_updates` for what changed on the tenders the team follows: deadline changes, clarifications, cancellations and awards. Lead with anything that needs action this week.
-2. Call `assess_tender_fit` with no tender to rank the open tenders that fit the saved company profile. If there's no profile, ask what the company does and where, then use `search_tenders` with `published_since` set to seven days ago.
-3. For the best three, give the buyer, value, closing date, the fit score and the one reason for and against that matters most. Link each notice.
-4. Offer the next step for one of them: the bid or no-bid call (the bid-or-no-bid skill), or adding it to the pipeline with `add_to_pipeline`.
-
-- If a search finds nothing, call `get_coverage` before saying a tender isn't public, and say which sources were read and when.
-- Never promise a bid will win. Never mention Tenda's plans, prices or upgrades.
+---
+name: weekly-scan
+description: Go through this week's public tenders for the person's company, pick the few worth a look, and say what changed on the ones they follow.
+---
+
+# Weekly scan
+
+1. Call `get_tender_updates` for what changed on the tenders the team follows: deadline changes, clarifications, cancellations and awards. Lead with anything that needs action this week.
+2. Call `assess_tender_fit` with no tender to rank the open tenders that fit the saved company profile. If there's no profile, ask what the company does and where, then use `search_tenders` with `published_since` set to seven days ago.
+3. For the best three, give the buyer, value, closing date, the fit score and the one reason for and against that matters most. Link each notice.
+4. Offer the next step for one of them: the bid or no-bid call (the bid-or-no-bid skill), or adding it to the pipeline with `add_to_pipeline`.
+5. If the person wants the best new fits every weekday without asking, offer Tenda's morning shortlist: call `add_automation` with `template` "morning_shortlist", read its rules back, and call `turn_on_automation` only once they say yes.
+
+- If a search finds nothing, call `get_coverage` before saying a tender isn't public, and say which sources were read and when.
+- 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: weekly-scan\r\ndescription: Go through this week's public tenders for the person's company, pick the few worth a look, and say what changed on the ones they follow.\r\n---\r\n\r\n# Weekly scan\r\n\r\n1. Call `get_tender_updates` for what changed on the tenders the team follows: deadline changes, clarifications, cancellations and awards. Lead with anything that needs action this week.\r\n2. Call `assess_tender_fit` with no tender to rank the open tenders that fit the saved company profile. If there's no profile, ask what the company does and where, then use `search_tenders` with `published_since` set to seven days ago.\r\n3. For the best three, give the buyer, value, closing date, the fit score and the one reason for and against that matters most. Link each notice.\r\n4. Offer the next step for one of them: the bid or no-bid call (the bid-or-no-bid skill), or adding it to the pipeline with `add_to_pipeline`.\r\n\r\n- If a search finds nothing, call `get_coverage` before saying a tender isn't public, and say which sources were read and when.\r\n- Never promise a bid will win. Never mention Tenda's plans, prices or upgrades.\r\n"

AFTER

"---\nname: weekly-scan\ndescription: Go through this week's public tenders for the person's company, pick the few worth a look, and say what changed on the ones they follow.\n---\n\n# Weekly scan\n\n1. Call `get_tender_updates` for what changed on the tenders the team follows: deadline changes, clarifications, cancellations and awards. Lead with anything that needs action this week.\n2. Call `assess_tender_fit` with no tender to rank the open tenders that fit the saved company profile. If there's no profile, ask what the company does and where, then use `search_tenders` with `published_since` set to seven days ago.\n3. For the best three, give the buyer, value, closing date, the fit score and the one reason for and against that matters most. Link each notice.\n4. Offer the next step for one of them: the bid or no-bid call (the bid-or-no-bid skill), or adding it to the pipeline with `add_to_pipeline`.\n5. If the person wants the best new fits every weekday without asking, offer Tenda's morning shortlist: call `add_automation` with `template` \"morning_shortlist\", read its rules back, and call `turn_on_automation` only once they say yes.\n\n- If a search finds nothing, call `get_coverage` before saying a tender isn't public, and say which sources were read and when.\n- Never promise a bid will win. Never mention Tenda's plans, prices or upgrades.\n"

Full snapshot data

{
  "description": "Go through this week's public tenders for the person's company, pick the few worth a look, and say what changed on the ones they follow.",
  "included_files": [],
  "name": "weekly-scan",
  "skill_md_contents": "---\nname: weekly-scan\ndescription: Go through this week's public tenders for the person's company, pick the few worth a look, and say what changed on the ones they follow.\n---\n\n# Weekly scan\n\n1. Call `get_tender_updates` for what changed on the tenders the team follows: deadline changes, clarifications, cancellations and awards. Lead with anything that needs action this week.\n2. Call `assess_tender_fit` with no tender to rank the open tenders that fit the saved company profile. If there's no profile, ask what the company does and where, then use `search_tenders` with `published_since` set to seven days ago.\n3. For the best three, give the buyer, value, closing date, the fit score and the one reason for and against that matters most. Link each notice.\n4. Offer the next step for one of them: the bid or no-bid call (the bid-or-no-bid skill), or adding it to the pipeline with `add_to_pipeline`.\n5. If the person wants the best new fits every weekday without asking, offer Tenda's morning shortlist: call `add_automation` with `template` \"morning_shortlist\", read its rules back, and call `turn_on_automation` only once they say yes.\n\n- If a search finds nothing, call `get_coverage` before saying a tender isn't public, and say which sources were read and when.\n- Never promise a bid will win. Never mention Tenda's plans, prices or upgrades.\n"
}

SHA-256 of public snapshot: 5941498018eb92470b7024bc8c530c681bcb392be4c7e0dc502700ac6ae4c075