fimo 2.14.0 → 2.14.1-staging.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/assets/skills/fimo-studio/references/ai-chat/agents.md +1 -1
- package/assets/skills/fimo-studio/references/ai-chat/default-agents.md +3 -3
- package/assets/skills/fimo-studio/references/ai-chat/routines.md +5 -1
- package/dist/cli/bundle.json +1 -1
- package/dist/cli/index.js +1 -1
- package/package.json +8 -8
- package/release.json +2 -2
- package/templates/astro/package.json +3 -3
- package/templates/nextjs/package.json +4 -4
- package/templates/react-router/package.json +5 -5
- package/templates/sveltekit/package.json +3 -3
- package/templates/vite/package.json +5 -5
|
@@ -34,7 +34,7 @@ A new page an agent leaves for a person shows as a `drafts` block in the chat: o
|
|
|
34
34
|
- In an agent, the header shows its name alone and the message box reads **Message <name>**. An empty default agent greets in its own words and offers starter requests; its description stays in its settings. A starter is sent as shown, by anyone who can send messages.
|
|
35
35
|
- Ask the agent to change its instructions; it uses its `agent` tool, and the chat shows **Updated instructions** with **View change** (before and after).
|
|
36
36
|
- The agent's settings have **Summary** and **Instructions** (shared with everyone; empty means none) and an **Instruction history**, where **Restore previous** puts back the text a change replaced.
|
|
37
|
-
- A default agent is Fimo's: its name, summary, instructions and portrait cannot change on any plan. Fimo's routines on it can be switched off and on, or deleted (a deleted one stays deleted)
|
|
37
|
+
- A default agent is Fimo's: its name, summary, instructions and portrait cannot change on any plan. Fimo's routines on it can be switched off and on, run less often than Fimo set them (see Pace in `ai-chat/routines`), or deleted (a deleted one stays deleted); nothing else about them changes (`routine_is_default`). On Pro, the team can add routines of its own to a default agent or to an agent of its own (`routine_needs_pro` below Pro); any chat can create one on the agent whose work it is. A routine Fimo retires stops running and leaves the list.
|
|
38
38
|
- In text, an agent links another as `[Name](agent://id)`, shown as a chip that opens it.
|
|
39
39
|
|
|
40
40
|
## Default agents
|
|
@@ -4,18 +4,18 @@ Plans, setup and the rules every default agent follows are in `ai-chat/agents`.
|
|
|
4
4
|
|
|
5
5
|
## SEO (8 routines)
|
|
6
6
|
|
|
7
|
-
- **Technical SEO:** status, redirects, canonicals, sitemap, robots.txt, language, main heading, and what got worse since its last run: pages moved without a redirect and, with Search Console, old addresses Google still shows that the site no longer serves. Runs on changes, the first publish, a new domain, and every Monday.
|
|
7
|
+
- **Technical SEO:** status, redirects, canonicals, sitemap, robots.txt, language, main heading, and what got worse since its last run: pages moved without a redirect and, with Search Console, old addresses Google still shows that the site no longer serves, and pages of the domain another system serves (an app's sign-in, docs) that cost the site in search, told once with the fix and who owns it. Runs on changes, the first publish, a new domain, and every Monday.
|
|
8
8
|
- **Broken links:** links to the site's own pages that fail or pass through a redirect. Runs on changes; links to other sites on the 1st of each month.
|
|
9
9
|
- **Meta tags:** titles, descriptions and Open Graph previews that are missing, repeated, or too long or short (characters and pixels), and titles that do not end like the site's other titles. Runs on changes and every Monday.
|
|
10
10
|
- **Image SEO:** alt text, file names, and images over 200 KB. An image in the media library is rendered through Fimo's resizing; a file of the site is uploaded first. An image on another host gets a proposal for a smaller export.
|
|
11
11
|
- **Hreflang:** on a site in more than one language, each version lists the others.
|
|
12
12
|
- **Internal linking:** orphan pages, pages more than three clicks deep, and articles with no link to a hub or product page or more than eight links. Runs on changes and every Monday.
|
|
13
|
-
- **Keyword optimization** (every Tuesday, needs Search Console):
|
|
13
|
+
- **Keyword optimization** (every Tuesday, needs Search Console): pages ranking 4th to 20th. A page of another kind than the top results is left as is, with one offer to prepare that kind as a proposal (a small search: a note only). When the pages above win on links from other sites, it says so. Else it rewrites title and headings (8th to 20th; Meta tags owns titles at 4th to 7th) or proposes, with why, the section several top results cover and the page lacks. It links inside the site alone when the linking text has the words, else proposes the link. It judges a change against unchanged pages once Google rereads it, calls too few impressions too little data, and undoes a clear loss.
|
|
14
14
|
- **Keyword research** (2nd of each month): proposes at most five pages and asks which to write; the Content agent's Writing routine writes the ones picked.
|
|
15
15
|
|
|
16
16
|
The Monday runs of Technical SEO, Meta tags and Internal linking read every page of main's hosted preview, for what no single change shows (pages out of the sitemap, shared titles, title shape, orphan and deep pages). A run that a change started checks only the pages it touches, its first run too.
|
|
17
17
|
|
|
18
|
-
Alone, it points a link at a new address only after it checked that the address shows the same content in the same language, and otherwise removes a dead link and keeps its words; it adds a link on words the text already uses to name another page, keeps the 8 most useful links on a page with too many, shortens a title or description Google cuts from the same words (in a field only search reads, added to the type when needed, when the title is also the page's heading), sets the public address when the canonicals and sitemap agree on it, adds a 301 from an old address Google still shows once one live page clearly covers the same subject (none: the address stays gone; several: it asks), and gives a page whose address says nothing (`/blog/blog-post-9a32c70f0f`) a readable one from its title, with a 301 from the old one. A title, description, heading or link that any agent or person changed is not changed again for 8 weeks (Google
|
|
18
|
+
Alone, it points a link at a new address only after it checked that the address shows the same content in the same language, and otherwise removes a dead link and keeps its words; it adds a link on words the text already uses to name another page, keeps the 8 most useful links on a page with too many, shortens a title or description Google cuts from the same words (in a field only search reads, added to the type when needed, when the title is also the page's heading), sets the public address when the canonicals and sitemap agree on it, adds a 301 from an old address Google still shows once one live page clearly covers the same subject (none: the address stays gone; several: it asks), and gives a page whose address says nothing (`/blog/blog-post-9a32c70f0f`) a readable one from its title, with a 301 from the old one. A title, description, heading or link that any agent or person changed is not changed again for 8 weeks (Google shows the effect weeks after it rereads a page), unless it is a fault, and words a person rewrote after an agent changed them stay. Keyword research never changes the site alone.
|
|
19
19
|
|
|
20
20
|
## GEO (4 routines)
|
|
21
21
|
|
|
@@ -4,7 +4,9 @@ A routine is saved instructions that an agent runs in a thread of its own: by ha
|
|
|
4
4
|
|
|
5
5
|
## Create and change
|
|
6
6
|
|
|
7
|
-
Any chat, an agent's or a regular one, creates, changes, runs and deletes the project's routines with its `routines` tool. A person asks in any chat ("check the prices every Monday", "run after each publish", "pause the link sweep"), and the routine goes on the agent whose job it is. Studio only shows routines. Routines of your own need Pro; a default routine can only be switched off and on, or deleted.
|
|
7
|
+
Any chat, an agent's or a regular one, creates, changes, runs and deletes the project's routines with its `routines` tool. A person asks in any chat ("check the prices every Monday", "run after each publish", "pause the link sweep"), and the routine goes on the agent whose job it is. Studio only shows routines. Routines of your own need Pro; a default routine can only be switched off and on, run less often, or deleted.
|
|
8
|
+
|
|
9
|
+
**Pace:** an agent fits a routine's schedule to what its runs find. After some weeks of scheduled runs that find nothing new, the routine tells its agent, and the agent makes the schedule slower on its own, keeps the earlier schedule in its memory, and tells the team in one sentence ("I now check your search results once a month, because nothing changed for five weeks"). The routine's page shows the new schedule and next run. The agent puts the earlier schedule back when a run finds work again or a person asks. It never adds runs on its own, by a tighter schedule or a new trigger: it proposes them and waits for a person. A default routine's schedule can be made slower on any plan, never faster than Fimo set it (`routine_is_default`).
|
|
8
10
|
|
|
9
11
|
## Triggers
|
|
10
12
|
|
|
@@ -20,6 +22,8 @@ A trigger is set in words. Fimo checks them and says when the routine runs, or w
|
|
|
20
22
|
|
|
21
23
|
Comparing a field's old and new values ("the price goes up by 10%") is not supported. For what Fimo cannot see as an event (traffic, rankings, errors), the agent offers a schedule whose run checks it and stops when there is nothing to do.
|
|
22
24
|
|
|
25
|
+
**Unpublished sites:** until the site is published, a schedule runs a routine the first time and then only when a person wrote or opened a chat of the project, or pressed **Run now**, since its previous run; otherwise the slot is skipped, leaves no run, and the next slot asks again, so a site someone tried and left does not spend credits every week. Events and **Run now** always run.
|
|
26
|
+
|
|
23
27
|
**Chains:** what a routine changes, publishes or reports can start the agent's other routines, in chains of any length. Each routine runs at most once per change that started the chain, so routines never loop or multiply. A person's new change, or a run by hand or on a schedule, starts a new chain.
|
|
24
28
|
|
|
25
29
|
**Waiting events:** events that come in while a run is busy wait, then run together in the next run; the Runs list shows one run with its event count. A very large burst, such as a bulk import, runs in several runs, in order. The agent can make a routine's event runs wait until the changes stop for a set number of minutes (at most 2 hours from the first), then read them in one run. A yes/no question is then answered once for all the waiting changes, each entry once in its latest version; a change it says no to leaves the queue, and when it says no to all, no run starts. Default routines that read what changed wait 10 minutes after the last change (Technical SEO, Meta tags, Image SEO, Internal linking, AI readiness, Structured data, AI citation optimization, Content lifecycle, Translation, Accessibility, Mobile optimization, Brand compliance); Editable copy waits 30 minutes; those that guard the live site (Broken links, Hreflang, Cookie consent, Privacy and legal pages) run at once.
|