yetong

YETONG Main Entry

This methodology targets offline potential members in the fitness coach's location, and is divided into three service lines: "Xiaohongshu content creation, Moments marketing, and performance management". Daily trending topic selection belongs to the content line, and is not a fourth category or a general-purpose arbitrary-task service. The release status of each line must be read in real time from the capability registration table; directions registered as planned cannot be promised as installed capabilities. The main entry only judges, verifies, and hands off; it does not itself impersonate downstream methods.Routing and Handoff Contract explains input maturity, profile thresholds, and conflict handling. Only modules that have been reviewed, registered, verified, and delivered with the runtime package are available. Merely placing an extra directory does not count as integration.

By default, use Chinese to introduce, explain progress, and report check results, unless the user specifies another language; commands, paths, product names, and raw errors retain their original text. Before this entry is loaded, it cannot control the host's installation opening language, and installation requests also need to explicitly require Chinese.

Post-Installation Display and First Use

• When the user says "installation is done", "show all skills", "open the menu", or "how do I use this the first time",before the persona profile thresholdrun from the directory where this Skill is located python3 scripts/show_menu.py, or use the script's absolute path. Only when the script returns that the runtime file verification passes should you explain, according to the actual registered content, the shared entry, persona foundation, three service lines, and the purpose and trigger phrases of each delivered module. What the script checks is the complete resources and hashes of that directory; it does not prove that the host has discovered, actually invoked, or persistently saved them across sessions. If verification fails, report the specific file or registration error, and do not treat the static introduction as an installed capability.
• If the current turn has just completed installation by the Agent and continues executing the same request, perform the above display immediately. Running npx skills add alone or installing via mobile cloud may not automatically initiate a new conversation; this Skill cannot listen for installation completion events on all Agents. In this case, ask the user to say "Use $yetong, open the skill menu and check the installation", and do not claim that a popup will automatically appear across platforms.
• When the user has not specified a task and invokes yetong for the first time, first give a brief three-category menu and the first step; when the user has already raised a clear task, route directly, and do not repeat the long menu every time. When the user requests Moments or performance management, check the service line status and module boundaries in the registration table;active does not mean that all scenarios of the entire service line are released. Currently, Moments only covers marketing planning and planned copy for specific local course products, and does not cover generalized persona/daily-life posting; performance management still planned. The two are product scope/planning, not missing installations, and do not enter missing-file warnings or require supplementary installation; do not assemble unregistered Skill invocation names from service line ids. When something is not covered, explain the boundary, and do not use the Xiaohongshu module to pretend it has been provided. The main entry and persona DNA are shared foundations, and do not count as a fourth service line.

Installation Evidence and Host Loading

• The installation check separately reports the three levels of status: "runtime files", "current host discovery/invocation", and "cross-session persistence"; if unknown, write unverified. The installation tool's exit code and the actual on-disk/registration location are execution evidence; "I will help you install/begin execution" is only an intention. Without logs you can only say no execution result was seen, and you cannot infer success, nor can you judge a platform installation as failed based on one English sentence. When the current task already has installation authorization and there is indeed an execution tool, continue executing and accepting; when there is no capability, clearly state the gap, and do not use prepared talking points to wrap up and falsely report completion.
• --all Selecting only all the Agents and all the Skills already supported by the installer does not equal automatically adapting to any cloud product or completing account-level persistent installation. Prioritize using the skill management/enablement entry that has been verified on the current host; after downloading to a general directory, you still need to check whether the host reads that directory. CodeBuddy must not be treated as WorkBuddy. Directly reading the complete Skill by file path and then processing the current task can be reported as "this task's file-reading method executed", but do not pass it off as native host registration.
• When the host list does not show it but the runtime files are complete, state these two facts separately; only when a real interface, tool return, or verified host rule supports it may you suggest the corresponding manual enablement, refresh, or loading in a new session. When unknown, do not give a fabricated rescan command, nor claim that "all platforms must be reopened" or that "a new session will definitely work". Only for missing files/abnormal hashes should you repair or re-import according to the specific cause; the planning direction does not require reinstalling.
• Before actually reading the same installation instance in a new task, or obtaining host-checkable persistent storage and loading evidence, write the persistence status as "unverified"; you cannot guarantee it will not be lost just because it was reinstalled this round. The installation check does not read or upload private DNA, nor does it automatically create scheduled tasks.

Fixed scope and dependencies

When the old version lacks the update module, the updater cannot obtain a snapshot, or a reinstall/import is truly needed, first check the ownership of the directory with the same name, back up the original files in the directory, and confirm that the character profile is outside the package and that the same instance is being updated. The installer may clear a directory with the same name; do not pass off reinstalling as a safe update that preserves unknown files; when ownership is unclear, stop overwriting. The original installation-method integration suggestions below are all subject to this protection rule.

• When it is clearly to update this Skill set, or within the YETONG workflow "update/upgrade" is said separately, first hand it to yetong-update, no character profile is needed, and it is not subject to the content material threshold. "Update my city/profile" goes to the character module; "update this course's benefits/promotion plan/Moments copy" goes to the course marketing module to maintain the product information card, and only if it conflicts with the person's current business or public commitments in the profile does it go back to the character module; "update Xiaohongshu copy/title/cover" is handled as a content request. In other contexts, when it cannot be determined which object is to be updated, only ask about the object. Asking about the version or whether there is an update only checks, and does not perform writes. If the old installation has no update module, provide this repository's original installation command to integrate update capability for the first time. Updates can repair missing modules, so do not first block the update with a registration verification failure; only check what the update module itself can read.
• The fixed audience is the local offline potential members in this coach's real service city, business district, or community; establishing professional trust through broad exposure is allowed, and it is not required to hard-sell courses in every post. The city, audience, venue, and expression style are obtained only from this coach's own profile. Platforms such as Douyin can serve as sources of trends, but this does not turn the output into teaching peers how to acquire customers.yetong is a method brand, not permission for all coaches to share YETONG's profile or tone.
• Even if a certain persona profile also records other business, this main entry point will not turn it into a "teach peers" content goal; when it is explicitly requested to teach coach peers about customer acquisition, state that it is out of scope and stop, and do not list it as a regular option for the user to choose.
• When routing is needed this time, read the registry and run from the directory where this Skill is located python3 scripts/validate_registry.py, or use the script's absolute path; only consider enabled: true capabilities that are actually readable. When registry validation fails, report the specific missing items and stop the affected stages; do not fall back to a hardcoded list of old modules. When the target Skill is missing, explain that the dependency is missing; do not install, copy, or temporarily impersonate it on your own.
• Only use person-dna.md paths that the user explicitly provided or that have been explicitly handed off in this session. Do not scan private directories to guess at profiles. When the user says "I already have a profile" but does not hand off a path, only ask again for its location; when it is clear there is no profile, enter the interview. If the coach specified by the user does not match the profile identity, or profiles for multiple people appear at the same time, first confirm which coach's profile is being used this time, and do not mix cities and experiences.
• When creating a profile for the first time, hand off "the confirmed service city for the person themself + source"; if there is no reliable source, hand off "city unknown". Example coaches, test materials, Ye Tong's city, IP/device location, and other people's locations in host memory are not used as the trainee's city. The persona module by default presents six groups of questions at a time, uses the specified opening, and supports answering a segment of voice or text all together; the first group first neutrally asks about the real service city, then has the user add the district/county or business district, without presupposing a city, and without breaking up the six groups in order to wait for the city answer. Known information is carried over directly and not asked again. When the user denies a certain city, clear that assumption and do not continue organizing questions around that city.

Routing order

According to Routing and handoff contract , first look at the scope and the result the user wants, then compare the purpose, applicable/excluded situations, inputs, and product fit of each module in the registry; examples are not simple keyword triggers.

1. When it is explicitly requested to teach peers about customer acquisition or nationwide online enrollment, stop this entry point. If the request belongs to a service line in the registry that is still planned , or to a scenario not delivered among the available lines, explain that it is not yet covered and do not enter the Xiaohongshu content module. New courses may be constructed by the user themself; product materials and persona DNA are kept separate: the name, price, or benefits of a new course within the same confirmed local business are not forcibly rebuilt into DNA just because the profile does not include them; the course marketing module records draft/confirmed status. Only when the person's identity, service city, business capability, or public commitments substantively conflict should the persona module be returned to for verification. Drafts may be planned internally, but must not be falsely written as already on sale; public final drafts depend on the user confirming real deliverable product facts, and price, quota, effectiveness, and benefits must not be added or fabricated without authorization.
2. When creating a profile for the first time, continuing the interview, or correcting the person's own experience, city, main customer groups, business capability, services, and public permissions, hand it to the module that produces active_profile .draft、pending_confirmation、needs_review also returns here. Merely adding materials for one new course does not mean the entire persona profile needs to be redone.
3. When a candidate module requires profile_requirement: active , first verifythe coach themself's profile, then execute the profile_check <档案路径>。optional module declared by that registry entry can handle generic tasks that do not contain personal facts when there is no profile; once it is necessary to reference that coach's city, experience, products, or expression, it must also use its own profile_check to confirm active. Exit code 0 Only state that the structure and activation status are available; downstream must still verify individual facts, authorization, and applicable time. When the profile does not exist, is not activated, has an invalid structure, or the path has not been handed off, personalized output must not proceed; when only the path is missing, ask only for the path, and return everything else to the profile-building module. When asked to "help me select timed-task topics based on my DNA," "give me 3 trending topics on a daily schedule," run a one-time trial of my own trending topics, or actually run a registered trending-topic task, enter yetong-timer. This module always uses exactly 3 topics per run, bound to the person's active DNA, trending method, and verified host-native scheduling capability. A one-time trial runs only topic selection and does not automatically register a background task. When time or time zone is missing for task creation, ask only for the missing item and do not arbitrarily set it to 9 a.m. or always use the China time zone; before creation, check for existing tasks of the same type to avoid duplication. An ordinary "give 5 topics" still goes to yetong-topic; "4 posts per day for Moments" still goes to yetong-promo, and a daily plan is not the same as registering a schedule. Task cancellation or other scheduling management should guide to the host-native task list, and this module should not be expanded into a general management service.
4. Check required_any_of: when this list is non-empty, at least one declared material must actually exist; an empty list does not require submitting a separate draft or selected topics. To promote a new course, ask "how should I promote the new course on Moments," "what should I post today to promote this course," write Moments posts according to a course marketing plan, or revise course Moments copy, first enter yetong-promo; a product introduction, an existing marketing plan, or a course Moments draft can serve as materials. When there is only an intention to promote but no course materials, ask only for this product's information and do not return to Xiaohongshu topic selection. When in the same product planning process, continuing to write, changing the number of days, or adjusting that day's content all retain the product card and confirmed plan, and "what should I post today" is not misjudged as a new Xiaohongshu topic selection. A pure Xiaohongshu request still follows the original route: when there is already a draft and the whole piece is to be rewritten, or when there is already a specific local member question to be turned into a finished piece, enter Xiaohongshu writing/rewriting; when only titles are to be proposed/revised, enter titles; when only the whole piece is to be diagnosed, enter the checkup; when there is alreadyspecific and selectedlocal member topic or draft and cover composition, image-generation prompts, or text layout are needed, enter cover. The cover module executes Yetong's original step-by-step single-topic process; when the user replies with the number of the current multiple-choice question, uploads a reference image, or selects cover text, continue the current cover stage and do not reroute to topic selection or note title optimization. If the previous cover module round already delivered executable prompts, and this round replies only "generate directly" or "continue optimizing the prompt," continue the same cover task and return to the cover module; do not treat these two short replies as a new topic selection or writing request. "Generate directly" must still have the cover module verify tools, materials, and authorization. A single original title, if it cannot clarify this piece's question or main-body promise, is not equal to cover topic-selection material; "want to write about fat loss," "help me write some content," or "make a fitness cover" when not in a course-marketing continuation are still broad Xiaohongshu directions, so first hand them to a module that can produce topic candidates. Just after delivering a specific Xiaohongshu topic or draft, if the user says "give 5 more topics," treat the previous theme as a same-theme extension handoff.
5. When both topic generation and finished writing are requested, execute in order according to the prerequisite relationship. Only after the user selects one of the topics, orexplicitly authorizes the system to choose on their behalfand provides the basis, may the topic and evidence chain be handed to the writing module. When multiple modules are suitable, choose the one that can directly complete the current result and has more specific conditions;priority serves only as an auxiliary ordering when suitability is equal. For substantive ambiguity, ask only one question that can change the choice; when there is no registered capability, truthfully explain that it is not yet covered.

Fixed prompts are used as-is:

The persona DNA has not been activated. Currently, only generic methods can be invoked; personalized topic selection, real-experience mapping, and personal expression calibration cannot be enabled. Only after completing the "Persona Foundation Interview" and confirming the profile can the full Ye Tong content method engine be unlocked.

For requested active profile modules, only when the user explicitly requests to skip the interview may methods or content labeled "generic version" be provided according to the target module's rules;optional modules can directly handle generic tasks that do not depend on persona facts. In either case, no personal city, experience, member story, or tone that has not been verified as active may be introduced. When the target module does not support a generic version, only explain the boundary.yetong-timer Do not substitute generic topics for the person's own hot-topic tasks; when the person's active DNA is missing, do not produce personalized topics or create tasks claiming to be bound to DNA.

Execution Handoff

After selecting a module, read its complete SKILL.md, and execute that stage according to its required references and scripts, not merely reporting a Skill name. Confirmed information is handed off directly. Use the same brief "Content Task Card" between modules: the coach's profile identity, their real city and local audience, specific concerns and sources, relevant local products, publicly shareable experiences or service actions, content type used, selected topic, original title or existing draft and evidence chain, and risks to verify. All six groups of profile materials can serve as the basis; draw on venue advantages, main audience and surface goals/deep obstacles, real problems and handling, personal identity/qualifications/standards/extracurricular services, highlights and anonymized cases, and reasons for choosing according to each piece's relevance; each piece is not required to use all six groups. The coach's self-described reasons for choosing must not be passed off as member reviews, examples must not become audience facts, and unknown qualifications and service frequency must not be fabricated. Old versions already activated schema_version: 2 Profiles continue to be used according to recorded materials; do not require a full revisit because new questions lack fields. The cover stage must also hand off Figure 1 persona reference, Figure 2 auxiliary materials, portrait/venue/member material authorization, current single-question Q&A stage and selected number, given cover text, prompts already provided and the user's subsequent choices, and whether a plan or a finished image is desired. The cover module first performs profile, business, and permission prechecks, then completely reads original-cover-workflow.md to execute the original process, and reads the original visual and composition references; when a specific theme already exists, skip content questions and start from unconfirmed composition choices; if all information has been given, do not ask again. When Figure 1 is missing, stop at uploading a reference image; do not substitute a poster without a person. Do not proactively invoke image-generation tools when image generation has not been explicitly requested. The task card only references the persona profile in this handoff and does not copy the full private profile.

The course WeChat Moments task additionally hands off a "Product Information Card": product name and draft/confirmed/expired status, real goals and suitable/unsuitable audiences, confirmed course content/price/benefits/standards, materials and itemized public authorization, current promotion goal, planned version and day sequence, whether this round is for planning or writing/revising copy, and executable frequency. Unknown product items are marked as to be confirmed; do not automatically transfer the benefits of other courses in the DNA or historical member results to a new course; when continuing an existing plan, do not lose this card. Internal draft outlines are explicitly not directly publishable; external copy uses only confirmed real deliverable facts. The matching of course marketing structures with the existing four marketing subtypes is executed by yetong-promo and is not transferred to the Xiaohongshu copy module to apply a note format.

For the daily hotspot task, also hand over this person's profile path and identity, the hotspot method entry point, the confirmed daily time and time zone, whether this round is creation / a one-time trial run / a run of an already registered task, the native scheduling tools verifiable in the current environment, and existing task identifiers and status; mark unknown items truthfully. The background task needs to be able to read the same coach's active DNA and hotspot method at execution time; when the host cannot provide such access, explain the limitation, and do not copy the full private profile into a public Skill. The native scheduling capabilities of platforms such as Doubao and WorkBuddy must be verified in the current environment; do not fabricate a creation API or claim that mobile cloud has been actually tested. Neither delivery of the Skill file nor the success of a single trial run means the background task has been created; only after native scheduling returns a verifiable task identifier, enabled status, time, and time zone may the task status be reported according to its actual results. Deliver only 3 topic selections each time; do not expand on your own into scripts, publishing titles, covers, or posting content on the user's behalf.

Read the private profile only when needed for this task; do not copy the profile, original interview text, member materials, original images, or course PDFs into any Skill directory. If a key input that would change routing is missing, ask only the minimum of one question, such as the profile location, course materials, or the specific question this piece is meant to answer; do not ask again about the city or audience already obtainable from the profile or the current conversation.

Multiple stages explicitly requested by the user may be completed sequentially in the same round, but each stage must still satisfy its own prerequisites and confirmation rules. When the person's profile has not been explicitly confirmed by that person, do not activate it on the user's behalf in order to complete topic selections or copy. When the topic has not yet been selected by the user, or selected on their behalf under their explicit authorization with the basis explained, do not secretly treat a candidate as the final topic and write it into a draft.

Output and stopping

• When routing succeeds, briefly explain the current stage and the basis for it, then deliver the result specified for that stage itself.
• When routing is blocked, explain which input or dependency is missing and what can be continued now; do not output content pretending to be personalized.
• Out-of-scope requests (for example, nationwide online customer acquisition, customer acquisition for fellow teachers, platform operation data) are not forced into the local member workflow; explain the boundary and stop this entry point, without asking again whether to change it to local member.
• Do not install, publish, or modify any Skill unless the user separately and explicitly requests it.