ProvelyNo. Google Calendar API returns a success response when it accepts the request. Provely proves created, guests_invited and rescheduled as separate promises.
| Fact | Value |
|---|---|
| Skill version | 0.1.0 |
| Publisher | Built and signed by Provely. |
| Certification | Provisional |
| Last conformance run | 2026-09-05T12:00:00Z: 42 of 42 cases passed, 0 critical false VERIFIED |
| Provider API versions | v3.20260826 |
| Default provider API version | v3.20260826 |
| Compiled | 2026-09-05 |
| Manifest hash | caa9e3ed67f54457 |
| Manifest hash check | the document hashes to the value the manifest states |
| Signature | valid, key provely-skill-2026-09, trusted by this build |
What does this page prove?
| Claim | Proven by | Evidence | Status |
|---|---|---|---|
| The event exists with the intended title, start and end. It does not prove that a guest is on it, was told, or comes. | google_calendar.event.created | E2 + E3 | proven |
| The stored attendee list holds the addresses that the person named. It does not prove that Google mailed a guest, or that a guest accepted. | google_calendar.event.guests_invited | E2 + E3 | proven |
| The provider changed the event inside this operation, and the stored start and end name the new instants. It does not prove that a guest was told. | google_calendar.event.rescheduled | E3 | proven |
| An outcome outside Google Calendar API, such as a bank credit or a person who read a message | not proven | no E5 channel | not proven |
| The meaning of a Google Calendar API state that no source states | not proven | no source states it | not proven |
| The agent report that the action worked | never counts | E0 | not proven |
Which completion levels does the Google Calendar API skill expose?
Each level is one promise with one contract. An agent picks the level that matches the promise it makes. It cannot upgrade a level. Read the completion level definition.
| Level | Contract | Promise | Evidence | Certification |
|---|---|---|---|---|
created | google_calendar.event.created v1.0.0 | The event exists with the intended title, start and end. It does not prove that a guest is on it, was told, or comes. | E2 + E3 | Provisional |
guests_invited | google_calendar.event.guests_invited v1.0.0 | The stored attendee list holds the addresses that the person named. It does not prove that Google mailed a guest, or that a guest accepted. | E2 + E3 | Provisional |
rescheduled | google_calendar.event.rescheduled v1.0.0 | The provider changed the event inside this operation, and the stored start and end name the new instants. It does not prove that a guest was told. | E3 | Provisional |
Which ways can a Google Calendar API action look done and not be?
| Contract | Case | Verdict |
|---|---|---|
| google_calendar.event.created | duplicate side effect | CONTRADICTED |
| google_calendar.event.created | pre existing state | CONTRADICTED |
| google_calendar.event.created | wrong subject | CONTRADICTED |
| google_calendar.event.guests_invited | duplicate side effect | CONTRADICTED |
| google_calendar.event.guests_invited | partial completion | CONTRADICTED |
| google_calendar.event.guests_invited | pre existing state | CONTRADICTED |
| google_calendar.event.guests_invited | wrong subject | CONTRADICTED |
| google_calendar.event.rescheduled | duplicate side effect | CONTRADICTED |
What did the last conformance run show?
The last conformance run on 2026-09-05T12:00:00Z passed 42 of 42 cases with 0 critical false VERIFIED. One critical false VERIFIED rejects a skill.
| Contract | Certification |
|---|---|
google_calendar.event.created | Provisional |
google_calendar.event.guests_invited | Provisional |
google_calendar.event.rescheduled | Provisional |
The weakest contract is google_calendar.event.created. It reaches Provisional. The package level is Provisional, because a package level never rises above its weakest contract. Read the level of the contract you use.
| Case class | Passed | Total |
|---|---|---|
| duplicate side effect | 3 | 3 |
| error after execution | 3 | 3 |
| error before execution | 3 | 3 |
| evidence unavailable | 3 | 3 |
| pre existing state | 3 | 3 |
| stale readback | 3 | 3 |
| still transitional | 3 | 3 |
| terminal success | 3 | 3 |
| timeout after commit | 3 | 3 |
| version mismatch | 3 | 3 |
| webhook duplicate | 3 | 3 |
| webhook out of order | 3 | 3 |
| wrong subject | 3 | 3 |
| wrong terminal state | 3 | 3 |
The conformance artifact digest is 0856d592b05a3fc8. The harness signs the run, so a reader can check that these numbers come from that run.
What remains uncertain?
The level is Provisional because of it. Provely does not guess a rule that a source does not state.
Where do these facts come from?
Every claim above cites a source assertion in the skill provenance. The compiler records the source, its hash, and the retrieval date. A page never states a provider rule without one.
| Source | Kind | Retrieved | Excerpt |
|---|---|---|---|
| google_calendar.docs.events | docs | 2026-09-09 | authored |
| google_calendar.docs.push | docs | 2026-09-09 | authored |
| google_calendar.docs.times | docs | 2026-09-09 | authored |
| google_calendar.docs.versions | docs | 2026-09-09 | authored |
| google_calendar.events | event sample | 2026-09-09 | authored |
| google_calendar.openapi | openapi | 2026-09-09 | trimmed |
How do I verify a Google Calendar API action?
Verify a Google Calendar API action with Provely
- Begin the operation.Call
beginwith the contractgoogle_calendar.event.createdand the input. Keep the operation id. - Make the Google Calendar API call you make today.Send the request with the correlation metadata that
beginreturned. - Submit the acknowledgement.Call
action_resultwith the Google Calendar API response. This is evidence level E1. It is not completion. - Verify.Call
verify. The runtime reads the evidence that the contract names, from Google Calendar API and not from the agent, and evaluates the contract. - Report the verdict exactly as returned.VERIFIED comes with a signed receipt. PENDING comes with the operation id. CONTRADICTED and UNVERIFIABLE are not success.
Questions developers ask
Does the created level prove the rescheduled level?
No. The event exists with the intended title, start and end. It does not prove that a guest is on it, was told, or comes. The provider changed the event inside this operation, and the stored start and end name the new instants. It does not prove that a guest was told. Use google_calendar.event.rescheduled to prove rescheduled.
Which Google Calendar API API versions does the skill support?
v3.20260826. An operation on another version returns UNVERIFIABLE with the reason version_unsupported. The runtime never guesses.
Does Provely need write access to Google Calendar API?
No. The agent keeps its write key. The verifier reads with a separate read-only credential where Google Calendar API permits it, and it never shares that credential with the agent.