hirify-cli 0.4.4 → 0.4.5

package/bin/hirify.js

@@ -1596,7 +1596,8 @@ Where to apply
 
 Applying
   Most vacancies here came from somewhere else: company pages, Telegram channels, other
-  boards. For those, reveal brings back the address and the person applies themselves.
+  boards. For those, reveal brings back the address, and the application is made there rather
+  than through Hirify.
   Vacancies hosted on Hirify can be applied to from here:
 
     hirify profile list

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "hirify-cli",
-  "version": "0.4.4",
+  "version": "0.4.5",
   "description": "Hirify CLI for AI agents: browser sign-in, job feeds, search, reading a vacancy in full, contacts to apply to, and applying on Hirify.",
   "bin": {
     "hirify": "bin/hirify.js"

package/skills/hirify/SKILL.md

@@ -75,8 +75,9 @@ the guide, it says so; then ask the user what to filter on.
 Two cases, two commands:
 
 - **Hosted on Hirify** -> `hirify vacancy apply <slug>` sends the application through Hirify.
-- **From somewhere else** -> `hirify vacancy reveal <slug>` gives the link or contact, and **the
-  user applies themselves**. `vacancy apply` refuses these and says so.
+- **From somewhere else** -> `hirify vacancy reveal <slug>` gives the link or contact, and the
+  application goes there rather than through Hirify. `vacancy apply` refuses these and says so.
+  What you do with that destination is between you and your user.
 
 - **Ask first, every time, and show what you are about to send.** An application cannot be taken
   back. Never apply to a list on a single "yes".

package/skills/hirify/reference.md

@@ -148,8 +148,8 @@ The last line before that says which way to apply:
 
 - `Apply on Hirify: hirify vacancy apply <slug>` - the vacancy is hosted here.
 - `Where to apply: hirify vacancy reveal <slug> (uses 1 reveal)` - it came from elsewhere, so the
-  user applies themselves. Take this from `vacancy read` rather than finding out from a refusal on
-  `vacancy apply`.
+  application goes to that destination rather than through Hirify. Take this from `vacancy read`
+  rather than finding out from a refusal on `vacancy apply`.
 
 Contacts, the apply destination and where the vacancy came from are never in this answer. That is
 what `vacancy reveal` is for.
@@ -199,8 +199,8 @@ Answers:
   where they choose to.
 - `there is no vacancy with that slug.`
 - a refusal in the server's own words, which covers archived, flagged, someone else's profile, and
-  **vacancies not hosted on Hirify**. For those, use `vacancy reveal` and let the user apply
-  themselves.
+  **vacancies not hosted on Hirify**. For those, use `vacancy reveal` and apply at the destination it
+  returns.
 - `the application could not be sent right now.` means our side failed, not the user's data.
 
 ## Saved searches and delivery